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

NPE when triggering downstream job

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Critical
    • Resolution: Fixed
    • core
    • Jenkins 1.621+
      all platforms

    Description

      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)

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-29807 NullPointerException when triggering dependent builds

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-30132 Null Pointer Exception with disabled downstream job

          • Major - Major loss of function.
          • Resolved
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-29794 race conditions in Triggers

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Web Link jenkins/pull/1842

          Activity

            Ascending order - Click to sort in descending order
            mlemanczyk Marek Lemanczyk created issue -
            mlemanczyk Marek Lemanczyk made changes -
            Field Original Value New Value
            Description 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}
            		 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}
            mlemanczyk Marek Lemanczyk made changes -
            Description 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}
            		 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}
            mlemanczyk Marek Lemanczyk made changes -
            Description 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}
            		 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}
            rdesgroppes Régis Desgroppes made changes -
            Link This issue is related to JENKINS-29807 [ JENKINS-29807 ]
            rdesgroppes Régis Desgroppes made changes -
            Link This issue is related to JENKINS-30132 [ JENKINS-30132 ]
            integer Kanstantsin Shautsou made changes -
            Assignee Kanstantsin Shautsou [ integer ]
            integer Kanstantsin Shautsou made changes -
            Remote Link This issue links to "jenkins/pull/1842 (Web Link)" [ 13163 ]
            integer Kanstantsin Shautsou made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            integer Kanstantsin Shautsou made changes -
            Link This issue is related to JENKINS-29794 [ JENKINS-29794 ]
            integer Kanstantsin Shautsou made changes -
            Link This issue is duplicated by JENKINS-29807 [ JENKINS-29807 ]
            integer Kanstantsin Shautsou made changes -
            Link This issue is related to JENKINS-29807 [ JENKINS-29807 ]
            integer Kanstantsin Shautsou made changes -
            Link This issue is duplicated by JENKINS-30132 [ JENKINS-30132 ]
            integer Kanstantsin Shautsou made changes -
            Link This issue is related to JENKINS-30132 [ JENKINS-30132 ]
            integer Kanstantsin Shautsou made changes -
            Summary NPE when triggering downstream job (again) NPE when triggering downstream job
            jmellor John Mellor made changes -
            Environment Jenkins 1.621+
            Windows 2003             		Jenkins 1.621+
            all platforms
            integer Kanstantsin Shautsou made changes -
            Labels dependencies permissions trigger trigger
            integer Kanstantsin Shautsou made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            scm_issue_link SCM/JIRA link daemon made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels trigger lts-candidate trigger
            integer Kanstantsin Shautsou made changes -
            Labels lts-candidate trigger trigger
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 164953 ] JNJira + In-Review [ 197585 ]
            linkmjb Matthew Bates made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            danielbeck Daniel Beck made changes -
            Resolution Fixed [ 1 ]
            Status Reopened [ 4 ] Resolved [ 5 ]

            People

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

              Dates

                Created:
                Updated:
                Resolved: