• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • Jenkins 1.621+
      all platforms

      We've some jobs which do some generic tasks. On success they are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.

      There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.

      Instead of triggering all the downstream jobs they fire this 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
      Triggering a new build of .....OUR PROJECT NAME...
      FATAL: null
      java.lang.NullPointerException
      at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111)
      at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84)
      at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141)
      at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245)
      at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687)
      at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
      at hudson.model.Run.execute(Run.java:1788)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:98)
      at hudson.model.Executor.run(Executor.java:381)

          [JENKINS-29876] NPE when triggering downstream job

          Marek Lemanczyk created issue -
          Marek Lemanczyk made changes -
          Description Original: We've some jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.

          There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.

          Instead of triggering the all the downstream jobs they fire this NPE:
          {quote}Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Triggering a new build of .....OUR PROJECT NAME...
          FATAL: null
          java.lang.NullPointerException
          at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111)
          at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84)
          at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141)
          at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245)
          at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687)
          at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
          at hudson.model.Run.execute(Run.java:1788)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:98)
          at hudson.model.Executor.run(Executor.java:381){quote}
          New: We've some jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.

          There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.

          Instead of triggering all the downstream jobs they fire this NPE:
          {quote}Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Triggering a new build of .....OUR PROJECT NAME...
          FATAL: null
          java.lang.NullPointerException
          at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111)
          at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84)
          at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141)
          at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245)
          at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687)
          at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
          at hudson.model.Run.execute(Run.java:1788)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:98)
          at hudson.model.Executor.run(Executor.java:381){quote}
          Marek Lemanczyk made changes -
          Description Original: We've some jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.

          There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.

          Instead of triggering all the downstream jobs they fire this NPE:
          {quote}Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Triggering a new build of .....OUR PROJECT NAME...
          FATAL: null
          java.lang.NullPointerException
          at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111)
          at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84)
          at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141)
          at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245)
          at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687)
          at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
          at hudson.model.Run.execute(Run.java:1788)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:98)
          at hudson.model.Executor.run(Executor.java:381){quote}
          New: We've some jobs which does some generic jobs. On success they are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.

          There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.

          Instead of triggering all the downstream jobs they fire this NPE:
          {quote}Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Triggering a new build of .....OUR PROJECT NAME...
          FATAL: null
          java.lang.NullPointerException
          at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111)
          at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84)
          at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141)
          at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245)
          at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687)
          at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
          at hudson.model.Run.execute(Run.java:1788)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:98)
          at hudson.model.Executor.run(Executor.java:381){quote}
          Marek Lemanczyk made changes -
          Description Original: We've some jobs which does some generic jobs. On success they are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.

          There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.

          Instead of triggering all the downstream jobs they fire this NPE:
          {quote}Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Triggering a new build of .....OUR PROJECT NAME...
          FATAL: null
          java.lang.NullPointerException
          at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111)
          at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84)
          at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141)
          at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245)
          at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687)
          at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
          at hudson.model.Run.execute(Run.java:1788)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:98)
          at hudson.model.Executor.run(Executor.java:381){quote}
          New: We've some jobs which do some generic tasks. On success they are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.

          There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.

          Instead of triggering all the downstream jobs they fire this NPE:
          {quote}Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Triggering a new build of .....OUR PROJECT NAME...
          FATAL: null
          java.lang.NullPointerException
          at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111)
          at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84)
          at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141)
          at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245)
          at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687)
          at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
          at hudson.model.Run.execute(Run.java:1788)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:98)
          at hudson.model.Executor.run(Executor.java:381){quote}
          Régis Desgroppes made changes -
          Link New: This issue is related to JENKINS-29807 [ JENKINS-29807 ]

          Also having the same issue on v1.624:
          Many of the gateway build jobs are not triggering dependency jobs breaking the build chains for the components. This is 100% for some jobs but not all.

          Error when this occurs:
          Notifying upstream projects of job completion
          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 jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111)
          at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84)
          at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141)
          at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245)
          at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687)
          at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
          at hudson.model.Run.execute(Run.java:1788)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:98)
          at hudson.model.Executor.run(Executor.java:381)

          linda mcdonald added a comment - Also having the same issue on v1.624: Many of the gateway build jobs are not triggering dependency jobs breaking the build chains for the components. This is 100% for some jobs but not all. Error when this occurs: Notifying upstream projects of job completion 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 jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111) at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84) at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245) at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687) at hudson.model.Build$BuildExecution.cleanUp(Build.java:200) at hudson.model.Run.execute(Run.java:1788) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381)
          Régis Desgroppes made changes -
          Link New: This issue is related to JENKINS-30132 [ JENKINS-30132 ]

          Still happening w/ 1.627. Rolling back to 1.620.

          Régis Desgroppes added a comment - Still happening w/ 1.627. Rolling back to 1.620.

          Peter Pakos added a comment -

          Still happening with 1.628.

          Peter Pakos added a comment - Still happening with 1.628.

          kgiloo added a comment -

          very silly bug.
          i was able to workaround it for some of my projects, removing "disabled" jobs from the downstreams.

          but for some other tasks without 'disabled' downstream jobs, it happens also.
          i do not get it.

          kgiloo added a comment - very silly bug. i was able to workaround it for some of my projects, removing "disabled" jobs from the downstreams. but for some other tasks without 'disabled' downstream jobs, it happens also. i do not get it.

            integer Kanstantsin Shautsou
            mlemanczyk Marek Lemanczyk
            Votes:
            11 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: