• Type: New Feature
• Resolution: Unresolved
• Priority: Major
• Component/s: copyartifact-plugin
• Labels:

  None

1. copyartifact-plugin-trojanbug.zip

   92 kB

   2013-02-17 10:31

[JENKINS-16847] Support for copying artifacts from other builds being part of the same MultiJob (previous phases)

Krzysztof Trojan created issue - 2013-02-17 10:31

Collapse comment: Krzysztof Trojan added a comment - 2013-02-17 11:13

Krzysztof Trojan added a comment - 2013-02-17 11:13

Could you please take a look if the contribution could be made part of the next version, I would prefer not to depend on branched code in my builds.

Expand comment: Krzysztof Trojan added a comment - 2013-02-17 11:13

Krzysztof Trojan added a comment - 2013-02-17 11:13 Could you please take a look if the contribution could be made part of the next version, I would prefer not to depend on branched code in my builds.

Krzysztof Trojan made changes - 2013-02-17 11:13

Assignee

New: Alan Harder [ mindless ]

Collapse comment: Krzysztof Trojan added a comment - 2013-02-17 14:09

Krzysztof Trojan added a comment - 2013-02-17 14:09

Created a pull request (finally on my machine ):
https://github.com/jenkinsci/copyartifact-plugin/pull/16

Expand comment: Krzysztof Trojan added a comment - 2013-02-17 14:09

Krzysztof Trojan added a comment - 2013-02-17 14:09 Created a pull request (finally on my machine ): https://github.com/jenkinsci/copyartifact-plugin/pull/16

Collapse comment: Alan Harder added a comment - 2013-02-17 22:08

Alan Harder added a comment - 2013-02-17 22:08

Please ask on the dev alias for someone to accept the pull request, or to get access so you can submit it yourself, thanks!

Expand comment: Alan Harder added a comment - 2013-02-17 22:08

Alan Harder added a comment - 2013-02-17 22:08 Please ask on the dev alias for someone to accept the pull request, or to get access so you can submit it yourself, thanks!

Alan Harder made changes - 2013-02-17 22:08

Assignee

Original: Alan Harder [ mindless ]

Collapse comment: Emmanuel Grumbach added a comment - 2013-03-18 20:50

Emmanuel Grumbach added a comment - 2013-03-18 20:50

I would also be very interested in this feature

Expand comment: Emmanuel Grumbach added a comment - 2013-03-18 20:50

Emmanuel Grumbach added a comment - 2013-03-18 20:50 I would also be very interested in this feature

Collapse comment: Ray Sennewald added a comment - 2014-10-07 21:53

Ray Sennewald added a comment - 2014-10-07 21:53

I've added a pull request for this functionality, albeit with a new Selector (MultiJobSelector). I've also added support for grabbing the artifact from a PhaseJob in another PhaseJob or in the parent MultiJob itself: https://github.com/jenkinsci/copyartifact-plugin/pull/49.

Expand comment: Ray Sennewald added a comment - 2014-10-07 21:53

Ray Sennewald added a comment - 2014-10-07 21:53 I've added a pull request for this functionality, albeit with a new Selector (MultiJobSelector). I've also added support for grabbing the artifact from a PhaseJob in another PhaseJob or in the parent MultiJob itself: https://github.com/jenkinsci/copyartifact-plugin/pull/49 .

Collapse comment: Krzysztof Trojan added a comment - 2014-10-08 13:55

Krzysztof Trojan added a comment - 2014-10-08 13:55

Ray, while useful, adding a new selector makes it possible to run the job only within MultiJob.

What if one wanted to use also in regular pipelines (project triggered both as part of MultiJob and by another project) ?
In the sense the original concept would I think work better ?

Expand comment: Krzysztof Trojan added a comment - 2014-10-08 13:55

Krzysztof Trojan added a comment - 2014-10-08 13:55 Ray, while useful, adding a new selector makes it possible to run the job only within MultiJob. What if one wanted to use also in regular pipelines (project triggered both as part of MultiJob and by another project) ? In the sense the original concept would I think work better ?

Krzysztof Trojan made changes - 2014-10-08 13:56

Description

Original: 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 a decent diff on the machine I am writing this on (sorry!).

New: 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 and a corresponding pull request.

Load more newer events