-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 1.598 on Linux
Workflow:Aggregator plugin 1.2
CopyArtifact plugin: 1.34
If I use the CopyArtifact plugin with a workflow step(), it correctly pulls the latest successful build's artifacts when pointed to a project of type Workflow.
However, if I specify parameters for that same project, it will always throw an AbortException saying no build with those parameters could be found, regardless of what I entered in.
If I change the CopyArtifact to point to a freestyle project, the parameters correctly work as intended, pulling in most recent build that had those parameters.
Since the CopyArtifact is behaving as it should, I'm assuming there's a flaw in how the Workflow plugin is exposing its build Parameters.
Sample code:
step ([$class: 'CopyArtifact', projectName: 'Test Run Composer', target: 'composer_run', parameters: "PRODUCT=test,BRANCH_NAME=$branch_name" ]);
- is related to
-
JENKINS-30357 CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
-
- Closed
-
-
JENKINS-32209 NodeLabel parameter not working inside workflow
-
- Closed
-
[JENKINS-26694] Workflow build Parameters are not exposed to CopyArtifact
Component/s | Original: workflow-plugin [ 18820 ] | |
Assignee | Original: Jesse Glick [ jglick ] | New: Tom FENNELLY [ tfennelly ] |
Labels | Original: copyartifact workflow-plugin | New: workflow |
Assignee | Original: Tom FENNELLY [ tfennelly ] | New: ikedam [ ikedam ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 160769 ] | New: JNJira + In-Review [ 208388 ] |
Labels | Original: workflow | New: pipeline workflow |