-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Linux Redhat 9
When triggering one pipeline job with parameters and disabling its downstream job, while building, if refreshing this job URL page, it send "Oops!" error message.
When using Jenkins-2.346 and "Parameterized Trigger plugin-2.45" did not have this issue
Curent Jenkins version is 2.449 and "Parameterized Trigger plugin" version is 787.v665fcf2a_830b_
Maybe this issue is related to "Build Pipeline" plugin. Its version is upgraded from 1.5.8 to 2.0.1
[JENKINS-72929] Jenkins job status wrong when triggering with parameters and disabling some downstream jobs
Description |
Original:
When triggering one pipeline job with parameters and disabling its downstream job, while building, if refreshing this job URL page, it send "Oops!" error message.
When using Jenkins-2.346 and "Parameterized Trigger plugin-2.45" did not have this issue |
New:
When triggering one pipeline job with parameters and disabling its downstream job, while building, if refreshing this job URL page, it send "Oops!" error message.
When using Jenkins-2.346 and "Parameterized Trigger plugin-2.45" did not have this issue Curent Jenkins version is 2.449 and "Parameterized Trigger plugin" version is 787.v665fcf2a_830b_ |
Component/s | New: build-pipeline-plugin [ 15962 ] | |
Description |
Original:
When triggering one pipeline job with parameters and disabling its downstream job, while building, if refreshing this job URL page, it send "Oops!" error message.
When using Jenkins-2.346 and "Parameterized Trigger plugin-2.45" did not have this issue Curent Jenkins version is 2.449 and "Parameterized Trigger plugin" version is 787.v665fcf2a_830b_ |
New:
When triggering one pipeline job with parameters and disabling its downstream job, while building, if refreshing this job URL page, it send "Oops!" error message.
When using Jenkins-2.346 and "Parameterized Trigger plugin-2.45" did not have this issue Curent Jenkins version is 2.449 and "Parameterized Trigger plugin" version is 787.v665fcf2a_830b_ Maybe this issue is related to "Build Pipeline" plugin. Its version is upgraded from 1.5.8 to 2.0.1 |
Component/s | Original: parameterized-trigger-plugin [ 15592 ] |
Component/s | New: multijob-plugin [ 16545 ] | |
Component/s | Original: build-pipeline-plugin [ 15962 ] |