-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[JENKINS-48431] - Support both lightweight checkout AND build parameter #898
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
Closed
Closed
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
5bd9173
JENKINS-48431 Support both lightweight checkout AND build parameters
bf791e2
Bugfix for tests
96f458d
Trim whitespaces
cb53320
Bugfix spotbugs
efe53fd
Merge branch 'master' into JENKINS-48431
MarkEWaite 4e4d5fd
Merge branch 'master' into JENKINS-48431
MarkEWaite 2243149
Merge branch 'master' into JENKINS-48431
jetersen 5825807
deduplicate and implement both GitSCMTelescope and GitSCMFileSystem
jetersen 274e66b
remove null check for build
jetersen 3cc1567
apply suggestions from @tgatinea
jetersen c424a69
remote can potentially be null
jetersen 49dee32
Merge branch 'master' into JENKINS-48431
MarkEWaite 4efe4e4
Merge branch 'master' into JENKINS-48431
MarkEWaite a1ebe5e
Merge branch 'master' into JENKINS-48431
MarkEWaite File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I discovered that this doesn't behave in quite the same way for statically provided strings vs environment variables in that by expanding the variable here rather than earlier we're forgoing some of the input normalization being done above.
example:
*/masterwill becomerefs/remotes/origin/master(probably) whereas${SOME_ENV_VAR}whose value is*/masterwill becomerefs/remotes/origin/*/masterwhich will NPE a little later on in the code.Obviously it's easy enough to just not include */ in the variable but it may also be worthwhile for variables and static strings to go through the same process of string normalization. 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*/mastervsmasterdoes not make any difference when expansion is not used? I wonder why is it supported in non-expansion mode in this case. Perhaps keep expansion as implemented here and consider changing non-expansion version later?