Added URL encode to HTTP GET to check if target remote job is parameterized #4
Conversation
This file contains 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
parameterized. Previously, a remote job with spaces in the name would cause a failure while attempting to check for job parameters. This caused each build trigger step to retry the parameterization check 5 times and then swallow the resulting AbortException.
|
plugins » parameterized-remote-trigger-plugin #15 SUCCESS |
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
morficus
added a commit
that referenced
this pull request
Jul 6, 2014
Added URL encode to HTTP GET to check if target remote job is parameterized
|
PLEASE ship the fix for |
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, a remote job with spaces in the name would
cause a failure while attempting to check for job parameters. This
caused each build trigger step to retry the parameterization check 5
times and then swallow the resulting AbortException.