• Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • core
    • None
    • Jenkins 1.561 RHEL6

      I have a job that is configured to trigger downstream job as a post build action. It gives me the following NPE:

      Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
      FATAL: null
      java.lang.NullPointerException
      at hudson.model.Result.isBetterOrEqualTo(Result.java:125)
      at hudson.tasks.BuildTrigger$2.shouldTriggerBuild(BuildTrigger.java:285)
      at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:243)
      at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:674)
      at hudson.model.Build$BuildExecution.cleanUp(Build.java:193)
      at hudson.model.Run.execute(Run.java:1755)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:231)

      This is happening only in 1.561 and works fine in 1.556

          [JENKINS-22821] NPE when triggering downstream job

          Gavin Hanover added a comment -

          this appears to be a new feature. see JENKINS-16956

          Gavin Hanover added a comment - this appears to be a new feature. see JENKINS-16956

          Daniel Beck added a comment -

          This is probably related to the splitting of the triggers and a field not being set correctly.

          What happens when you re-save the affected jobs' configurations? Just open the job config page and click Save without changing anything. Does that fix it?

          Other than that, `getThreshold()` should probably be used in `shouldTriggerBuild` rather than the potentially null `threshold`.

          Daniel Beck added a comment - This is probably related to the splitting of the triggers and a field not being set correctly. What happens when you re-save the affected jobs' configurations? Just open the job config page and click Save without changing anything. Does that fix it? Other than that, `getThreshold()` should probably be used in `shouldTriggerBuild` rather than the potentially null `threshold`.

          Loading and saving the configuration page fix the bug for me, thanks!

          Gwen Georgeault added a comment - Loading and saving the configuration page fix the bug for me, thanks!

          Daniel Beck added a comment -

          Closing this then.

          Daniel Beck added a comment - Closing this then.

          Daniel Beck added a comment -

          A comment to JENKINS-23191 by Donato describes a problem with the JavaScript on the job config page that can result in this issue. See there for a workaround.

          Daniel Beck added a comment - A comment to JENKINS-23191 by Donato describes a problem with the JavaScript on the job config page that can result in this issue. See there for a workaround.

          Andrew Herron added a comment -

          I can reproduce this, more info in JENKINS-23083. Re-saving configurations didn't help.

          Andrew Herron added a comment - I can reproduce this, more info in JENKINS-23083 . Re-saving configurations didn't help.

            Unassigned Unassigned
            eguess74 eguess74
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: