• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • Jenkins 1.590
      Fedora release 20 (Heisenbug) x86_64
      OpenJDK Runtime Environment 1.7.0_71-mockbuild_2014_10_15_17_02-b00

      We've some jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs.

      But instead of triggering the jobs they fire this NPE:

      First time build. Skipping changelog.
      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 jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:133)
      	at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:83)
      	at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:140)
      	at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:243)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:699)
      	at hudson.model.Build$BuildExecution.cleanUp(Build.java:194)
      	at hudson.model.Run.execute(Run.java:1805)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      	at hudson.model.ResourceController.execute(ResourceController.java:89)
      	at hudson.model.Executor.run(Executor.java:240)
      

      There are a lot of JENKINS-Issues related to similar problems. But all of them are resolved fixed, cannot reproduce, or duplicated. So this seems to be a new problem.

          [JENKINS-25758] NPE when triggering downstream job (again)

          Steffen Sledz created issue -
          Steffen Sledz made changes -
          Link New: This issue is related to JENKINS-22821 [ JENKINS-22821 ]
          Steffen Sledz made changes -
          Link New: This issue is related to JENKINS-23686 [ JENKINS-23686 ]
          Steffen Sledz made changes -
          Link New: This issue is related to JENKINS-22397 [ JENKINS-22397 ]
          Steffen Sledz made changes -
          Link New: This issue is related to JENKINS-16956 [ JENKINS-16956 ]
          Steffen Sledz made changes -
          Labels New: dependencies trigger
          Steffen Sledz made changes -
          Labels Original: dependencies trigger New: dependencies permissions trigger
          Steffen Sledz made changes -
          Description Original: We've some trigger-only jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs only but fire this NPE:
          {noformat}
          First time build. Skipping changelog.
          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 jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:133)
          at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:83)
          at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:140)
          at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:243)
          at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:699)
          at hudson.model.Build$BuildExecution.cleanUp(Build.java:194)
          at hudson.model.Run.execute(Run.java:1805)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:89)
          at hudson.model.Executor.run(Executor.java:240)
          {noformat}

          There are a lot of JENKINS-Issues related to similar problems. But all of them are resolved *fixed*, *cannot reproduce*, or *duplicated*. So this seems to be a new problem.
          New: We've some jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs.

          But instead of triggering the jobs they fire this NPE:

          {noformat}
          First time build. Skipping changelog.
          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 jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:133)
          at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:83)
          at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:140)
          at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:243)
          at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:699)
          at hudson.model.Build$BuildExecution.cleanUp(Build.java:194)
          at hudson.model.Run.execute(Run.java:1805)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:89)
          at hudson.model.Executor.run(Executor.java:240)
          {noformat}

          There are a lot of JENKINS-Issues related to similar problems. But all of them are resolved *fixed*, *cannot reproduce*, or *duplicated*. So this seems to be a new problem.

          Daniel Beck added a comment -

          This looks a lot like JENKINS-23191. Make sure the downstream project (the one with the trigger defined) has one of the result options selected.

          Daniel Beck added a comment - This looks a lot like JENKINS-23191 . Make sure the downstream project (the one with the trigger defined) has one of the result options selected.
          Steffen Sledz made changes -
          Link New: This issue duplicates JENKINS-23191 [ JENKINS-23191 ]

            Unassigned Unassigned
            sledz Steffen Sledz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: