jenkinsci / jenkinsci/parameterized-trigger-plugin
[JENKINS-33178] Build pipeline displays incorrectly when triggering the same project multiple times with different parameters
- Dominant language
- Java
- Stars
- 77
- Forks
- 174
- Avg merge
- 22h 27m
- Merged PRs (30d)
- 1
Description
OS: Ubuntu 14.04 (64-bit)
openjdk version "1.8.0_72-internal"
OpenJDK Runtime Environment (build 1.8.0_72-internal-b15)
OpenJDK 64-Bit Server VM (build 25.72-b15, mixed mode)
Jenkins ver. 1.642.1
Parameterized trigger plugin 2.30
Checkstyle plugin 3.44
I have a project which calls another project (using the parameterized trigger plugin) multiple times with different parameters (I am passing different version of php to use while running unit tests / checkstyle). "Block until the triggered projects finish their builds" is checked. When the build executes, the build pipeline plugin displays the same data for both builds. When the first downstream build is building, both pipeline items display the same info about the first build. Then when the second downstream build starts building, both pipeline items display info about the second build.
---
Originally reported by
jebmeier, imported from: Build pipeline displays incorrectly when triggering the same project multiple times with different parameters
Raw content of original issue
OS: Ubuntu 14.04 (64-bit)
openjdk version "1.8.0_72-internal"
OpenJDK Runtime Environment (build 1.8.0_72-internal-b15)
OpenJDK 64-Bit Server VM (build 25.72-b15, mixed mode)
Jenkins ver. 1.642.1
Parameterized trigger plugin 2.30
Checkstyle plugin 3.44I have a project which calls another project (using the parameterized trigger plugin) multiple times with different parameters (I am passing different version of php to use while running unit tests / checkstyle). "Block until the triggered projects finish their builds" is checked. When the build executes, the build pipeline plugin displays the same data for both builds. When the first downstream build is building, both pipeline items display the same info about the first build. Then when the second downstream build starts building, both pipeline items display info about the second build.
Contributor guide
Assessment
This issue has not been assessed yet.