Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-68189

Downstream jobs are no longer executed (regression in 2.341)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core
    • Jenkins 2.341
    • 2.343

      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.

        1. Capture d’écran, le 2022-04-04 à 10.02.04.png
          Capture d’écran, le 2022-04-04 à 10.02.04.png
          115 kB

          [JENKINS-68189] Downstream jobs are no longer executed (regression in 2.341)

          Francis Labrie created issue -
          Francis Labrie made changes -
          Attachment New: Capture d’écran, le 2022-04-04 à 10.02.04.png [ 57620 ]
          Francis Labrie made changes -
          Description Original: 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:
          {code:java}
          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
          {code}
          But now, there is no such output anymore:
          {code:java}
          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
          {code}
          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.           		New: 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:
          {code:java}
          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
          {code}
          But now, there is no such output anymore:
          {code:java}
          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
          {code}
          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.

          !Capture d’écran, le 2022-04-04 à 10.02.04.png|thumbnail!
          Basil Crow made changes -
          Link New: This issue is caused by JENKINS-67237 [ JENKINS-67237 ]
          Jesse Glick made changes -
          Labels New: regression
          Basil Crow made changes -
          Remote Link New: This issue links to "jenkinsci/jenkins#6447 (Web Link)" [ 27539 ]
          Basil Crow made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Basil Crow made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Basil Crow made changes -
          Summary Original: Downstream jobs are no longer executed New: Downstream jobs are no longer executed (regression in 2.341)
          Basil Crow made changes -
          Released As New: 2.343
          Assignee New: Mark Waite [ markewaite ]
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Fixed but Unreleased [ 10203 ]
          Basil Crow made changes -
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]

            markewaite Mark Waite
            flabrie Francis Labrie
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: