JENKINS-52341 - added logic to handle project residing under sub-folder #12
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
|
Looks good to me! Thank you for your contribution! :) |
|
Great, thanks :) |
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.
This is a fix for defect: https://issues.jenkins-ci.org/browse/JENKINS-52341
Older logic was assuming that if argument job contains character "/" then it is a matrix project. But this was causing conflict when a normal Jenkins job exists under some sub-folder. This fix will check if the parent item to the job is Matrix project then will be processed accordingly. If it is not Matrix project then it will simply get item by full name (to resolve the full Jenkins job path).
Verified by building the plugin locally and on local Jenkins.