| We recently upgraded to 1.651.31 and are not able run maven jobs due to the following exception: 23:57:33 Set build name.
23:57:33 New build name is '#1079-origin/geneva'
23:57:33 Parsing POMs
23:57:33 Established TCP socket on 58860
23:57:33 maven31-agent.jar already up to date
23:57:33 maven31-interceptor.jar already up to date
23:57:33 maven3-interceptor-commons.jar already up to date
23:57:33 [commons-test-parent] $ java -Xmx1024m -Xms512m ...
23:57:34 <===[JENKINS REMOTING CAPACITY]===>channel started
23:57:34 ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com
23:57:34 java.lang.NullPointerException
23:57:34 at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:305)
23:57:34 at hudson.maven.ProcessCache.get(ProcessCache.java:236)
23:57:34 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:778)
23:57:34 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
23:57:34 at hudson.model.Run.execute(Run.java:1738)
23:57:34 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
23:57:34 at hudson.model.ResourceController.execute(ResourceController.java:98)
23:57:34 at hudson.model.Executor.run(Executor.java:410)
23:57:34 project=hudson.maven.MavenModuleSet@489d6650[geneva/commons-test-master] It looks like this is the culprit: commit 9bd5bae03184777cd9280b8bced78793f39699b1
Author: Jesse Glick <jgl...@cloudbees.com>
Date: Wed Jul 17 17:12:03 2013 -0400 [FIXED JENKINS-18403] Detect when an attempt is made to run Maven on JDK 5.
If so, retry with (6+) slave JVM, setting maven- {compiler,surefire} -plugin properties to point to original.
Originally-Committed-As: 288b8d0b01f92072d0b86efb898c011f31a7fc30 |
