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

Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized-trigger-plugin will lead to a non working pipeline

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Jenkins LTS 1.532.1
      BlameSubversion plugin 1.200

      Creating two freestyle jobs, A and B.
      Settings in A:

      • Post-build Actions:
      • - Trigger parameterized builds on other projects: build "B" without parameters
      • - UpDownStreamNumberSychronizedNotify, number = 10

      Then trigger A manually. Build of B does not start.
      Log (A #3):

      Building remotely on Slave1 in workspace C:\build_jen\workspace\A
      B #30 is already in the queue
      Notifying upstream projects of job completion
      Finished: SUCCESS

        Attachments

          Activity

          Hide
          alex01ves Alex Vesely added a comment -

          Still the same with 1.565.1.

          Show
          alex01ves Alex Vesely added a comment - Still the same with 1.565.1.
          Hide
          boldie Sven S. added a comment - - edited

          The problem still exists within 1.638. Once a pipeline has been created and if the UpDownStreamNumberSychronizedNotify was set once the error can not be removed by removing UpDownStreamNumberSychronizedNotify. This is a really blocker for us, because for the moment we have a build-server with many such jobs which are now broken.

          After further investigations, I found out, this problem can be temporary fixed by removing the UpDownStreamNumberSychronizedNotify and then restarting the jenkins itself.

          Show
          boldie Sven S. added a comment - - edited The problem still exists within 1.638. Once a pipeline has been created and if the UpDownStreamNumberSychronizedNotify was set once the error can not be removed by removing UpDownStreamNumberSychronizedNotify. This is a really blocker for us, because for the moment we have a build-server with many such jobs which are now broken. After further investigations, I found out, this problem can be temporary fixed by removing the UpDownStreamNumberSychronizedNotify and then restarting the jenkins itself.

            People

            • Assignee:
              Unassigned
              Reporter:
              alex01ves Alex Vesely
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: