-
New Feature
-
Resolution: Fixed
-
Major
-
None
I'd like to be able to copy artifacts from the last stable build of a job that was run with a given set of parameters. That is, for JOB1 with parameters PARAM1 and PARAM2, I'd like to be able to tell JOB2 to copy artifacts from the last build of JOB1 that had PARAM1=Bob,PARAM2=Alice. The existing syntax for specifying matrix jobs might be reusable, thus:
Project Name: JOB1/PARAM1=Bob,PARAM2=Alice
Bonus points for parameter expansion, so that JOB2's parameters could be used to make the selection:
Project Name: JOB1/PARAM1=$THISPARAM,PARAM2=$THATPARAM
- depends on
-
JENKINS-13222 Allow job selection with fixed job names to contain variables without requiring job permissions for authenticated users
-
- Closed
-
I like the idea of specifying the parameters in the same way as a matrix configuration, but it seems too hacky to code that way.. I'd need a fake "job" to pass to the BuildSelector API that only returns builds with matching parameters. But then you could pick any of the available selector types..
Much easier would be to add a new BuildSelector for this.. so you'd just put the job name in the first box, then choose "parameterized build" or something in the selector list.. this would give you a textbox to enter the param1=value1¶m2=value2 bit.. but then this selector needs to know which build that matches those parameters to pick. Probably here I'd just go by status, stable/unstable. Does this sound ok?