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

NPE when triggering downstream job

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Component/s: core
    • Labels:
      None
    • Environment:
      Jenkins 1.561 RHEL6
    • Similar Issues:

      Description

      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

        Attachments

          Issue Links

            Activity

            Hide
            glhanove Gavin Hanover added a comment -

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

            Show
            glhanove Gavin Hanover added a comment - this appears to be a new feature. see JENKINS-16956
            Hide
            danielbeck 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`.

            Show
            danielbeck 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`.
            Hide
            ggeorgea Gwen Georgeault added a comment -

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

            Show
            ggeorgea Gwen Georgeault added a comment - Loading and saving the configuration page fix the bug for me, thanks!
            Hide
            danielbeck Daniel Beck added a comment -

            Closing this then.

            Show
            danielbeck Daniel Beck added a comment - Closing this then.
            Hide
            danielbeck 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.

            Show
            danielbeck 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.
            Hide
            spyder Andrew Herron added a comment -

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

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

              People

              • Assignee:
                Unassigned
                Reporter:
                eguess74 eguess74
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: