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

Finishing with a Null Pointer Exception after a successful build.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • maven-plugin
    • None
    • Tomcat 7.020, Windows 7, Jenkins 1.426, Perforce SCM, using the Perforce plug in.

      Each build is successful, but at the end of the build, the following is reported.
      [INFO] ------------------------------------------------------------------------
      [INFO] Reactor Summary:
      [INFO]
      [INFO] cciAdapter ........................................ SUCCESS [0.577s]
      [INFO] cciAdapter-core ................................... SUCCESS [2.655s]
      [INFO] cciAdapter-ftp .................................... SUCCESS [1.092s]
      [INFO] cciAdapter-ws Spring-WS Application ............... SUCCESS [0.996s]
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD SUCCESS
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 6.257s
      [INFO] Finished at: Tue Aug 16 14:11:50 BST 2011
      [INFO] Final Memory: 19M/123M
      [INFO] ------------------------------------------------------------------------
      Waiting for Jenkins to finish collecting data
      channel stopped
      FATAL: null
      java.lang.NullPointerException
      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:833)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:448)
      at hudson.model.Run.run(Run.java:1376)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:479)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:230)

      Full log file is attached.

          [JENKINS-10715] Finishing with a Null Pointer Exception after a successful build.

          Scott Marshall created issue -
          Scott Marshall made changes -
          Attachment New: upload.txt [ 20723 ]
          Description Original:
          Each build is successful, but at the end of the build, the following is reported.
          [INFO] ------------------------------------------------------------------------
          [INFO] Reactor Summary:
          [INFO]
          [INFO] cciAdapter ........................................ SUCCESS [0.577s]
          [INFO] cciAdapter-core ................................... SUCCESS [2.655s]
          [INFO] cciAdapter-ftp .................................... SUCCESS [1.092s]
          [INFO] cciAdapter-ws Spring-WS Application ............... SUCCESS [0.996s]
          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD SUCCESS
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 6.257s
          [INFO] Finished at: Tue Aug 16 14:11:50 BST 2011
          [INFO] Final Memory: 19M/123M
          [INFO] ------------------------------------------------------------------------
          Waiting for Jenkins to finish collecting data
          channel stopped
          FATAL: null
          java.lang.NullPointerException
          at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:833)
          at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:448)
          at hudson.model.Run.run(Run.java:1376)
          at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:479)
          at hudson.model.ResourceController.execute(ResourceController.java:88)
          at hudson.model.Executor.run(Executor.java:230)

          Full log file is attached.
          New: Each build is successful, but at the end of the build, the following is reported.
          [INFO] ------------------------------------------------------------------------
          [INFO] Reactor Summary:
          [INFO]
          [INFO] cciAdapter ........................................ SUCCESS [0.577s]
          [INFO] cciAdapter-core ................................... SUCCESS [2.655s]
          [INFO] cciAdapter-ftp .................................... SUCCESS [1.092s]
          [INFO] cciAdapter-ws Spring-WS Application ............... SUCCESS [0.996s]
          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD SUCCESS
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 6.257s
          [INFO] Finished at: Tue Aug 16 14:11:50 BST 2011
          [INFO] Final Memory: 19M/123M
          [INFO] ------------------------------------------------------------------------
          Waiting for Jenkins to finish collecting data
          channel stopped
          FATAL: null
          java.lang.NullPointerException
          at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:833)
          at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:448)
          at hudson.model.Run.run(Run.java:1376)
          at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:479)
          at hudson.model.ResourceController.execute(ResourceController.java:88)
          at hudson.model.Executor.run(Executor.java:230)

          Full log file is attached.
          kutzi made changes -
          Assignee New: kutzi [ kutzi ]

          kutzi added a comment -

          I had already fixed this in in https://github.com/jenkinsci/jenkins/commit/e7f17b5db283af591faf71aeb5f76af6626757cc
          If I had known that the NPE was already part of the 1.426 RC, I would have escalated the fix

          kutzi added a comment - I had already fixed this in in https://github.com/jenkinsci/jenkins/commit/e7f17b5db283af591faf71aeb5f76af6626757cc If I had known that the NPE was already part of the 1.426 RC, I would have escalated the fix
          kutzi made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]
          kutzi made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Thanks for the quick review. If I'm reading this correctly, then this will be fixed in the next release ?

          Scott Marshall added a comment - Thanks for the quick review. If I'm reading this correctly, then this will be fixed in the next release ?

          kutzi added a comment -

          Yes

          kutzi added a comment - Yes
          sogabe made changes -
          Link New: This issue is duplicated by JENKINS-10741 [ JENKINS-10741 ]

          This seems to be a blocker, at least for me, because since the upgrade to the latest version of Jenkins (Jenkins ver. 1.426) all my Maven-based builds fail! Env. Jenkins stand-alone, Linux Debian and Linux Ubuntu (both of them), Jenkins 1.426, one uses simply SVN, other GIT (so doesn't seem to be connected at all) - summing up, environment doesn't matter, builds just report failing in 1.426

          Krystian Nowak added a comment - This seems to be a blocker, at least for me, because since the upgrade to the latest version of Jenkins (Jenkins ver. 1.426) all my Maven-based builds fail! Env. Jenkins stand-alone, Linux Debian and Linux Ubuntu (both of them), Jenkins 1.426, one uses simply SVN, other GIT (so doesn't seem to be connected at all) - summing up, environment doesn't matter, builds just report failing in 1.426
          Krystian Nowak made changes -
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]

            kutzi kutzi
            scott_the_scot Scott Marshall
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: