-
Bug
-
Resolution: Fixed
-
Major
-
None
to reproduce the issue:
1. create a parameterized job called upstreamA with upstreamJobName parameter, add auto-downstream job as a downstream parameterized job, and add manual-downstream job as a manual downstream job
2. create a parameterized job called upstreamB with upstreamJobName parameter, add auto-downstream job as a downstream parameterized job, and add manual-downstream job as a manual downstream job
3. create a parameterized job called 'manual-downstream' with upstreamJobName parameter and set Build name to ${ENV,var="upstreamJobName"}-${BUILD_NUMBER} (have to use Set Build Name plugin)
4. create a parameterized job called 'auto-downstream' with upstreamJobName parameter and set Build name to ${ENV,var="upstreamJobName"}-${BUILD_NUMBER} (have to use Set Build Name plugin)
5. Create a build pipeline view named 'pipelineA' and set upstreamA as initial job
6. Create a build pipeline view named 'pipelineB' and set upstreamB as initial job
7. go to upstreamA and trigger the job with upstreamJobName = upstreamA
8. go to upstreamB and trigger the job with upstreamJobName = upstreamB
9. go to pipelineA view and trigger the manual downstream job
10. go to pipelineB view and trigger the manual downstream job
11. After a while, refresh pipelineA and pipelineB views' pages and then watch manual jobs' build names. Both will have the same names on manual jobs' builds.
- is related to
-
JENKINS-20485 Manual trigger cannot handle 'join' after fork, i.e. several upstream dependencies
- Open