![]() |
|
|
|
|
Change By:
|
Krzysztof Trojan
(08/Oct/14 1:56 PM)
|
|
Description:
|
Currently there is no easy way of selecting the right build to copy artifacts from if the project we want to copy from is part of MultiJob.
The "Last Successful Build" is prone for selecting the wrong build if the project was build again in the meantime between the MultiJob start and current moment
and "Upstream Project That Triggered this Build" does not work as previously executed builds in the same MultiJob are not considered "upstream" (are not listed as "causes").
A patch to TriggeredBuildSelector has been created to explicitly support MultiJob plugin pipelines and query it for builds already completed, treating them as if they were "causes". Somewhat dirty (for in for loop :) ), but works correctly and for the number of projects in a pipeline does not matter much.
See attachment
. Complete project as I did not have
and
a
decent diff on the machine I am writing this on (sorry!)
corresponding pull request
.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
