Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copyright Check takes a diff of the current branch versus master instead of the target branch. #962

Closed
dilijev opened this issue May 10, 2016 · 9 comments

Comments

@dilijev
Copy link
Contributor

dilijev commented May 10, 2016

It is still correct in the sense that it will get at least all of the files edited by a pull request, but it is checking a much larger set of files than necessary. Would be nice to clean this up.

@dilijev
Copy link
Contributor Author

dilijev commented May 16, 2016

@mmitche @tcare Do you know if there's any way to detect the base branch of a commit given only that commit hash (which I think is all that is available to Jenkins -- @mmitche correct me if I'm wrong).

I'm thinking this might actually be an impossible issue to solve.

@mmitche
Copy link
Contributor

mmitche commented May 16, 2016

@dilijev Actually a ton of other stuff is available:http://dotnet-ci.cloudapp.net/job/dotnet_corefx/job/master/job/ubuntu14.04_release_prtest/1194/parameters/

All those are available in the environment while running a task.

@dilijev
Copy link
Contributor Author

dilijev commented May 16, 2016

@mmitche Excellent! Just what I was looking for!

@dilijev
Copy link
Contributor Author

dilijev commented May 16, 2016

@mmitche Are those available in both windows and linux environment variables?

@dilijev
Copy link
Contributor Author

dilijev commented May 16, 2016

Note to self: the ones I will most likely be interested in are:
ghprbTargetBranch
ghprbSourceBranch

@mmitche
Copy link
Contributor

mmitche commented May 16, 2016

Yes, %ghprbTargetBranch% in batch, and $ghprbTargetBranch in shell. Make sure you escape the $ in the shell steps (in groovy) so that it will resolve at run-time and not generation time

@dilijev
Copy link
Contributor Author

dilijev commented May 16, 2016

@mmitche Yep, thanks for the reminder -- that's always a good way to trip things up.

@dilijev
Copy link
Contributor Author

dilijev commented Jun 14, 2016

@mmitche I was just thinking about this and I wonder if you know offhand if there would be a problem if the $ was used in a single-quoted string, since Groovy won't interpolate variables in single-quoted strings AFAIK?

@mmitche
Copy link
Contributor

mmitche commented Jun 14, 2016

@dilijev Nope it won't, so that makes it easy to do some of the shell scripting. You can also do:

$fooVar

@dilijev dilijev assigned boingoing and unassigned dilijev Oct 17, 2016
dilijev added a commit to dilijev/ChakraCore that referenced this issue Apr 28, 2017
dilijev added a commit to dilijev/ChakraCore that referenced this issue May 1, 2017
dilijev added a commit to dilijev/ChakraCore that referenced this issue May 5, 2017
Testing change to fix chakra-core#962
Comparative test of PR against current release/1.4
dilijev added a commit to dilijev/ChakraCore that referenced this issue May 5, 2017
dilijev added a commit to dilijev/ChakraCore that referenced this issue May 5, 2017
dilijev added a commit to dilijev/ChakraCore that referenced this issue May 6, 2017
Testing change to fix chakra-core#962
Comparative test of PR against current release/1.4
dilijev added a commit to dilijev/ChakraCore that referenced this issue May 6, 2017
dilijev added a commit to dilijev/ChakraCore that referenced this issue May 6, 2017
chakrabot pushed a commit that referenced this issue May 8, 2017
…Fix #2928: use Ubuntu 16.04 for style checks

Merge pull request #2933 from dilijev:jenkins-fixes

Replaces #2927

Fix #962: Copyright Check should check versus target branch instead of master.

See tests of the functionality in the following PRs:

- #2896 (release/1.4-ci)
- #2924 (release/1.4 test output comparison)
- #2925 (release/2.0-ci)
- #2926 (release/2.0 test output comparison)

Fix #2928: Update Style Checks to use Ubuntu16.04.

- Tested in #2929

Fixes #962
Fixes #2928
chakrabot pushed a commit that referenced this issue May 9, 2017
…get branch; Fix #2928: use Ubuntu 16.04 for style checks

Merge pull request #2933 from dilijev:jenkins-fixes

Replaces #2927

Fix #962: Copyright Check should check versus target branch instead of master.

See tests of the functionality in the following PRs:

- #2896 (release/1.4-ci)
- #2924 (release/1.4 test output comparison)
- #2925 (release/2.0-ci)
- #2926 (release/2.0 test output comparison)

Fix #2928: Update Style Checks to use Ubuntu16.04.

- Tested in #2929

Fixes #962
Fixes #2928
chakrabot pushed a commit that referenced this issue May 10, 2017
…ck versus target branch; Fix #2928: use Ubuntu 16.04 for style checks

Merge pull request #2933 from dilijev:jenkins-fixes

Replaces #2927

Fix #962: Copyright Check should check versus target branch instead of master.

See tests of the functionality in the following PRs:

- #2896 (release/1.4-ci)
- #2924 (release/1.4 test output comparison)
- #2925 (release/2.0-ci)
- #2926 (release/2.0 test output comparison)

Fix #2928: Update Style Checks to use Ubuntu16.04.

- Tested in #2929

Fixes #962
Fixes #2928
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants