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

NullPointerException when triggering dependent builds

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None
    • Ubuntu 12.04.1, Jenkins 1.621-1.624

      Build completes satisfactorily, but NPE while triggering dependent builds. I upgraded to 1.623 to see if that resolved the fault, but the results are identical. The log shows only 4 of 10 builds triggered, but it may not have been flushed at the point of the fault. All builds are freestyle using multiple shell steps, with no Java or Groovy components or steps. This problem is 100% repeatable with certain builds.

      Tail of an example failing build:
      17:44:08 Archiving artifacts
      17:44:11 Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
      17:44:11 Triggering a new build of trap
      17:44:11 Triggering a new build of snort-e
      17:44:11 Triggering a new build of tcparchive_982
      17:44:11 Triggering a new build of deepinspect
      17:44:11 FATAL: null
      17:44:11 java.lang.NullPointerException
      17:44:11 at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111)
      17:44:11 at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84)
      17:44:11 at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141)
      17:44:11 at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245)
      17:44:11 at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687)
      17:44:11 at hudson.model.Build$BuildExecution.cleanUp(Build.java:200)
      17:44:11 at hudson.model.Run.execute(Run.java:1788)
      17:44:11 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      17:44:11 at hudson.model.ResourceController.execute(ResourceController.java:98)
      17:44:11 at hudson.model.Executor.run(Executor.java:381)
      17:44:11 Finished: SUCCESS

          [JENKINS-29807] NullPointerException when triggering dependent builds

          Sverre Moe added a comment - - edited

          rdesgroppes Would rolling back to 1.620 work (solve the problem)?

          Sverre Moe added a comment - - edited rdesgroppes Would rolling back to 1.620 work (solve the problem)?

          John Mellor added a comment -

          The critical problem here is that all of the dependent builds after a disabled dependency in the list are not triggered, thus breaking the entire build tree. This means that in real use, the entire toolchain needs to externally work around Jenkins instead of relying on it. This affect a LOT of users. Can we please get this fixed in the 1.628 release?

          John Mellor added a comment - The critical problem here is that all of the dependent builds after a disabled dependency in the list are not triggered, thus breaking the entire build tree. This means that in real use, the entire toolchain needs to externally work around Jenkins instead of relying on it. This affect a LOT of users. Can we please get this fixed in the 1.628 release?

          djviking it doesn't solve the problem per se (we'd like to switch to a more recent Jenkins version) but, at least, it brings back our master into an acceptable state.

          Régis Desgroppes added a comment - djviking it doesn't solve the problem per se (we'd like to switch to a more recent Jenkins version) but, at least, it brings back our master into an acceptable state.

          Any idea on complexity to fix / timeline if someone is already taking a look at this?

          Peter Novotnak added a comment - Any idea on complexity to fix / timeline if someone is already taking a look at this?

          I'm seeing this same symptom/trace - however, I do NOT have a disabled build. Also tried with 1.627 with no luck, rolling back to 1.620 now to see if that works.

          Nathan Neulinger added a comment - I'm seeing this same symptom/trace - however, I do NOT have a disabled build. Also tried with 1.627 with no luck, rolling back to 1.620 now to see if that works.

          Sorry, actually, I DID have a disabled build... just missed it when reviewing the config. 1.620 definitely worked again for me as well.

          Nathan Neulinger added a comment - Sorry, actually, I DID have a disabled build... just missed it when reviewing the config. 1.620 definitely worked again for me as well.

          Peter Pakos added a comment -

          Still happening with 1.628.

          Peter Pakos added a comment - Still happening with 1.628.

          Daniel Beck added a comment -

          Duplicates JENKINS-29876.

          Daniel Beck added a comment - Duplicates JENKINS-29876 .

          Sverre Moe added a comment - - edited

          It is semantics, but actually JENKINS-29876 is the duplicate, since this issue was reported 5 days before.

          Sverre Moe added a comment - - edited It is semantics, but actually JENKINS-29876 is the duplicate, since this issue was reported 5 days before.

          Daniel Beck added a comment -

          True. I decided to resolve this way because that other issue has a similar number of watchers/votes, but the attention of Kostya.

          Daniel Beck added a comment - True. I decided to resolve this way because that other issue has a similar number of watchers/votes, but the attention of Kostya.

            Unassigned Unassigned
            jmellor John Mellor
            Votes:
            11 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: