-
Bug
-
Resolution: Fixed
-
Major
-
None
I have upgraded to Jenkins 1.530 and the build pipeline 1.4 plugin and now when a job in the pipeline fails or is aborted and the job is then re-executed to a successful completion, the job does not reflect a success and more importantly, the downstream job's trigger is NOT enables. This stops the pipeline in its tracks. I'm forced to create a entirely new pipeline.
- Initial job fails
- fix the underlying issue and hit the trigger on the failed job\
- the job does not indicate that it is re0running with the "yellow" in progress boc and the progress bar. if I look at the underlying job, I can see that it is running
- The job succeeds but the pipeline job is not upodated to "green" to reflect the sucess
- More importantly, the downstream job's trigger is not enabled.
- duplicates
-
-
- Resolved
-
-
-
- Resolved
-
- links to
[JENKINS-19870] Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds
Scott MacDonald
added a comment - Same issue on Jenkins 1.543 Pipeline 1.4.2 
Chris van Breeden
added a comment - Same issue on Jenkins 1.554.1 Pipeline 1.4.2
is there a workaround available??
Chris van Breeden
added a comment - Same issue on Jenkins 1.554.1 Pipeline 1.4.2
is there a workaround available?? 
eric wood
added a comment - Any chance that this can get fixed. This is super useful functionality. I have updated to all of the latest LTS 1.625.1 as well as the build pipeline plugin 1.4.8.
When I have a job fail and I fix the underlying issue and then hit the "re-try" trigger on the job, it shows that the next build was successful and then enables the downstream job to be able to run. If I refresh the page, it reverts back to the "failed" state with the initial job that failed showing as a failure and the upstream jobs all revert back to being "blue" or indicating that they were never run.
Help!
eric wood
added a comment - Any chance that this can get fixed. This is super useful functionality. I have updated to all of the latest LTS 1.625.1 as well as the build pipeline plugin 1.4.8.
When I have a job fail and I fix the underlying issue and then hit the "re-try" trigger on the job, it shows that the next build was successful and then enables the downstream job to be able to run. If I refresh the page, it reverts back to the "failed" state with the initial job that failed showing as a failure and the upstream jobs all revert back to being "blue" or indicating that they were never run.
Help!
Can you please re-test on master?
This is very similar to JENKINS-30801, the PR is very similar as well. JENKINS-30801 was fixed in master and it's likely it resolved this issue as well.
Same issue on Jenkins LTS 1.509.4 with plugin version 1.4.1