-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 1.413, Maven Integration plugin 1.413
I have a Maven job that fails occasionally with the following message:
ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.NullPointerException at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:560) at hudson.maven.Maven3Builder.end(Maven3Builder.java:220) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:723) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:429) at hudson.model.Run.run(Run.java:1374) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145) project=hudson.maven.MavenModuleSet@70f5f42b[MVN Gerrit Verification] project.getModules()=[hudson.maven.MavenModule@cebeab4[...(omitted)...] project.getRootModule()=hudson.maven.MavenModule@416baa61[...(omitted)...] FATAL: null java.lang.NullPointerException at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:560) at hudson.maven.Maven3Builder.end(Maven3Builder.java:220) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:723) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:429) at hudson.model.Run.run(Run.java:1374) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145)
The workaround is to re-trigger the job. I don't know the exact failure rate, but let's say 1 in 4 or 5.
