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.

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

              Created:
              Updated:
              Resolved: