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

ReverseBuildTrigger.threshold not consistently saved

      Created three jobs: job A, job B, job C. Set job B config to be triggered after job A and to trigger job C. In this case, radio button in the section "build after other projects are built" cannot be saved (even if you save and reopen the configuration page). When job A is built, a NullPointerException is thrown and job B is not started (see attachments). If you chain only job B to job A, it works.

          [JENKINS-23191] ReverseBuildTrigger.threshold not consistently saved

          Donato Tagliabue created issue -

          kutzi added a comment -

          This is in the normal downstream configuration of Jenkins and not in the Downstream-Ext plugin. Therefore changing component to core

          kutzi added a comment - This is in the normal downstream configuration of Jenkins and not in the Downstream-Ext plugin. Therefore changing component to core
          kutzi made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: downstream-ext [ 15682 ]

          Daniel Beck added a comment -

          Re-save all job configurations involved and try again. This is likely caused by JENKINS-16956 in 1.560.

          Daniel Beck added a comment - Re-save all job configurations involved and try again. This is likely caused by JENKINS-16956 in 1.560.

          Hi, I can confirm that the problem happens in Jenkins 1.563 with three new jobs created from scratch. When in project B you choose "Build after other projects are built" you have "Trigger only if build is stable" selected by default. When you add as a post-build action "Build other projects", none of the previous radio buttons are selected (it seems almost a javascript problem).
          If you save the configuration like that for the job B, and you run the job A, you'll get the error "java.lang.NullPointerException at hudson.model.Result.isBetterOrEqualTo(Result.java:125)" and job B will not be triggered.

          Donato Tagliabue added a comment - Hi, I can confirm that the problem happens in Jenkins 1.563 with three new jobs created from scratch. When in project B you choose "Build after other projects are built" you have "Trigger only if build is stable" selected by default. When you add as a post-build action "Build other projects", none of the previous radio buttons are selected (it seems almost a javascript problem). If you save the configuration like that for the job B, and you run the job A, you'll get the error "java.lang.NullPointerException at hudson.model.Result.isBetterOrEqualTo(Result.java:125)" and job B will not be triggered.

          Daniel Beck added a comment -

          Donato: Thanks for the explanation. I experience the same issue on 1.567.

          Annoying workaround: Re-set the 'trigger after other projects' threshold after adding a 'build other projects' post-build step, and whenever opening the config form again if there's a 'build other projects' configured.

          Daniel Beck added a comment - Donato: Thanks for the explanation. I experience the same issue on 1.567. Annoying workaround: Re-set the 'trigger after other projects' threshold after adding a 'build other projects' post-build step, and whenever opening the config form again if there's a 'build other projects' configured.
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-16956 [ JENKINS-16956 ]
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-22821 [ JENKINS-22821 ]

          Hi Daniel, the workaround works, but you have to do that every time you modify the job (let me say, if you change the description, you will also have to set the radio button for the downstream project trigger). From my personal experience, it's very easy to forget it.

          Donato Tagliabue added a comment - Hi Daniel, the workaround works, but you have to do that every time you modify the job (let me say, if you change the description, you will also have to set the radio button for the downstream project trigger). From my personal experience, it's very easy to forget it.
          Jesse Glick made changes -
          Assignee Original: kutzi [ kutzi ] New: Jesse Glick [ jglick ]

            jglick Jesse Glick
            donato73 Donato Tagliabue
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: