[
https://issues.jenkins-ci.org/browse/JENKINS-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Davidson reopened JENKINS-8657:
------------------------------------
I'm having some trouble with this feature on v1.21 of the copy artifact plugin.
I have a related job that has two build parameters: SIM_COMMON_REV and
SIM_INTERFACE_REV. The name of the job is sim-interfaces-linux64. When I
attempt to "copy artifacts" by providing both parameters in the project name
text box like so:
sim-interfaces-linux64/SIM_COMMON_REV=${SIM_COMMON_REV}&SIM_INTERFACE_REV=${SIM_INTERFACE_REV}
I receive the following build error: Unable to find a build for artifact copy
from: sim-interfaces-linux64/SIM_COMMON_REV=default&SIM_INTERFACE_REV=default
However, those values are completely valid, and I have a number of builds that
satisfy those conditions. If I only specify a single parameter (striking the
ampersand obviously) each works on it's own. It's only when combined that it
has problems.
Perhaps my syntax is incorrect, otherwise I think there is probably an issue.
> copy artifacts from last stable build of a parameterized job, by parameter
> --------------------------------------------------------------------------
>
> Key: JENKINS-8657
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8657
> Project: Jenkins
> Issue Type: New Feature
> Components: copyartifact
> Affects Versions: current
> Reporter: evilchili
> Assignee: Alan Harder
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
