Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
Jenkins 2.341
-
-
2.343
Description
Since Jenkins 2.341 (or one of the plugin update used by the downstream execution feature, if it's the case), jobs linked to upstream jobs are no longer executed after a successful build.
Before, upstream job build log did output something like this:
Build step 'Record compiler warnings and static analysis results' changed build result to UNSTABLE
Sending e-mails to: foo@xyz.com bar@xyz.com
[Slack Notifications] found #95 as previous completed, non-aborted build
[Slack Notifications] will send OnUnstableNotification because build matches and user preferences allow it
Lancement d'un nouveau build de XYZ Application » Production Web Bundle
Finished: UNSTABLE
But now, there is no such output anymore:
Build step 'Record compiler warnings and static analysis results' changed build result to UNSTABLE
Sending e-mails to: foo@xyz.com bar@xyz.com
[Slack Notifications] found #96 as previous completed, non-aborted build
[Slack Notifications] will send OnUnstableNotification because build matches and user preferences allow it
Finished: UNSTABLE
And checking the downstream job configuration, the **Build after other projects are built option is still checked, watching the expected job, with option Trigger even if the build is unstable on.
Attachments
Issue Links
- is caused by
-
JENKINS-67237 Downstream jobs are not guaranteed to build when the job configs have been updated recently
-
- Closed
-
- links to
Activity
Robin Pellatt
added a comment - I still get the problem with 2.342. Running Jenkins 2.342 and reverting the plugin to 2.43 appears to work in my installation.
Update 07/04/22 - The revert to 2.43 has now seemingly stopped triggering downstream jobs too.
Andy H
added a comment - - edited Running Jenkins 2.342 and reverting the plugin to 2.43 appears to work in my installation.
Update 07/04/22 - The revert to 2.43 has now seemingly stopped triggering downstream jobs too.
The revert of the breaking change just merged in the Jenkins master branch. Build is running at https://ci.jenkins.io/job/Core/job/jenkins/job/master/
I get the same except my build flow is structured the other way round, the build that succeeds has a post build action to build other jobs, but these are not being triggered. In the downstream build view it shows the other jobs as e.g.: