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

      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

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

          Alex Vesely created issue -

          Alex Vesely added a comment -

          Still the same with 1.565.1.

          Alex Vesely added a comment - Still the same with 1.565.1.

          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.

          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.
          Sven S. made changes -
          Component/s New: parameterized-trigger-plugin [ 15592 ]
          Sven S. made changes -
          Summary Original: UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 New: Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized build will lead to a non working pipeline
          Sven S. made changes -
          Summary Original: Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized build will lead to a non working pipeline New: Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized-trigger-plugin will lead to a non working pipeline
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 153016 ] New: JNJira + In-Review [ 178387 ]

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

              Created:
              Updated: