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

NPE on Maven3 Project - after Upgrading from 1.489 to 1.500

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      After upgrading Jenkins from Version 1.489 to 1.500 with reindexing, all the Maven3 Project doesnt work anymore.

      The same Build in the Freestyle Jobs works fine, but theres no possibility to run maven-release.

      Heres the error:

      18:59:40 [JENKINS] Archiving disabled
      18:59:41 Warte bis Jenkins die Datensammlung abgeschlossen hat
      18:59:41 mavenExecutionResult exceptions not empty
      18:59:41 message : Internal error: java.lang.NullPointerException
      18:59:41 cause : null
      18:59:41 Stack trace : 
      18:59:41 org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException
      18:59:41 	at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
      18:59:41 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
      18:59:41 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
      18:59:41 	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
      18:59:41 	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
      18:59:41 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
      18:59:41 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
      18:59:41 	at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
      18:59:41 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      18:59:41 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      18:59:41 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      18:59:41 	at java.lang.reflect.Method.invoke(Method.java:597)
      18:59:41 	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
      18:59:41 	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
      18:59:41 	at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
      18:59:41 	at hudson.maven.Maven3Builder.call(Maven3Builder.java:100)
      18:59:41 	at hudson.maven.Maven3Builder.call(Maven3Builder.java:66)
      18:59:41 	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
      18:59:41 	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
      18:59:41 	at hudson.remoting.Request$2.run(Request.java:326)
      18:59:41 	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
      18:59:41 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      18:59:41 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      18:59:41 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      18:59:41 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      18:59:41 	at java.lang.Thread.run(Thread.java:662)
      18:59:41 Caused by: java.lang.NullPointerException
      18:59:41 	at hudson.maven.reporters.TestMojo.getReportFiles(TestMojo.java:104)
      18:59:41 	at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:125)
      18:59:41 	at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:443)
      18:59:41 	at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:425)
      18:59:41 	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
      18:59:41 	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
      18:59:41 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228)
      18:59:41 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
      18:59:41 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
      18:59:41 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
      18:59:41 	... 24 more
      

      Any Ideas?

        Attachments

          Issue Links

            Activity

            Hide
            pmc123 P McHugh added a comment -

            I have the exact same problem, although it only appears to happen on projects which use the PHP maven plugin. I think it might have something to do with the test reporting target folder but so far no luck in working round it.

            Show
            pmc123 P McHugh added a comment - I have the exact same problem, although it only appears to happen on projects which use the PHP maven plugin. I think it might have something to do with the test reporting target folder but so far no luck in working round it.
            Hide
            cellsreinvent Steven Crellin added a comment - - edited

            I have the same problem on a Maven2 project, without the PHP maven plugin. I suspected the "Publish xUnit test result report" post-build action, but the job still fails with no post-build actions at all....

            Show
            cellsreinvent Steven Crellin added a comment - - edited I have the same problem on a Maven2 project, without the PHP maven plugin. I suspected the "Publish xUnit test result report" post-build action, but the job still fails with no post-build actions at all....

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bigboiler Jan Mederer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: