jenkinsci / jenkinsci/parameterized-trigger-plugin

[JENKINS-10861] Copy artifacts from downstream job run via synchronous Trigger Build step

Open
#492 2 comments 0 reactions 0 assignees View on GitHub
component:copyartifact-plugin component:parameterized-trigger-plugin enhancement imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
77
Forks
174
Avg merge
22h 27m
Merged PRs (30d)
1

Description

Add a new Copy Artifact option "Copy from downstream build".

This would only be useful if the job made use of the synchronous (wait to complete) usage of a "Trigger a Build" build step from the Parameterized Trigger Plugin.

When enabled, the plugin could query the downstream job, looking for any job whose UPSTREAM job matched the current job and build number. If one were found, artifacts from that build could be selected.

There would be a weird situation: if a job used MORE THAN ONE "Trigger a Build" in a synchronous fashion, then tried to retrieve artifacts from that build. If the default behavior was to copy artifacts from the MOST RECENT downstream build, that would be fine.

---
Originally reported by jswager1, imported from: Copy artifacts from downstream job run via synchronous Trigger Build step


  • status: Open
  • priority: Minor
  • component(s): copyartifact-plugin, parameterized-trigger-plugin
  • resolution: Unresolved
  • votes: 7
  • watchers: 9
  • imported: 2025-12-07

Raw content of original issue

Add a new Copy Artifact option "Copy from downstream build".

This would only be useful if the job made use of the synchronous (wait to complete) usage of a "Trigger a Build" build step from the Parameterized Trigger Plugin.

When enabled, the plugin could query the downstream job, looking for any job whose UPSTREAM job matched the current job and build number. If one were found, artifacts from that build could be selected.

There would be a weird situation: if a job used MORE THAN ONE "Trigger a Build" in a synchronous fashion, then tried to retrieve artifacts from that build. If the default behavior was to copy artifacts from the MOST RECENT downstream build, that would be fine.

  • environment: Typical Jenkins

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.