I managed to get out of the issue by cleaning up my pom.xml. It seems that Jenkins is a little more sensitive about the pom files. In our case here it had to do with dependency versions and/or typos in the custom properties.
On Friday, December 6, 2013 9:49:04 PM UTC-8, Stephane Odul wrote: > > 00:00:02.778 ERROR: Processing failed due to a bug in the code. Please > report this to jenkinsci-users@googlegroups.com > 00:00:02.780 java.lang.NullPointerException > 00:00:02.780 at > jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties(PomPropertiesFinder.java:38) > 00:00:02.780 at > jenkins.plugins.maveninfo.extractor.MavenInfoExtractor.extract(MavenInfoExtractor.java:58) > 00:00:02.780 at > jenkins.plugins.maveninfo.extractor.MavenInfoEnvironment.tearDown(MavenInfoEnvironment.java:42) > 00:00:02.780 at > hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:852) > 00:00:02.780 at > hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) > 00:00:02.780 at hudson.model.Run.execute(Run.java:1677) > 00:00:02.780 at > hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) > 00:00:02.780 at > hudson.model.ResourceController.execute(ResourceController.java:88) > 00:00:02.780 at hudson.model.Executor.run(Executor.java:231) > 00:00:02.780 > project=hudson.maven.MavenModuleSet@4c7b39a1[build-realtimedlp-trunk] > 00:00:02.781 > project.getModules()=[hudson.maven.MavenModule@11b9981a[build-realtimedlp-trunk/com.shn.dlp:realtimedlp][build-realtimedlp-trunk/com.shn.dlp:realtimedlp][relativePath:]] > 00:00:02.781 > project.getRootModule()=hudson.maven.MavenModule@11b9981a[build-realtimedlp-trunk/com.shn.dlp:realtimedlp][build-realtimedlp-trunk/com.shn.dlp:realtimedlp][relativePath:] > 00:00:02.781 FATAL: null > 00:00:02.781 java.lang.NullPointerException > 00:00:02.781 at > jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties(PomPropertiesFinder.java:38) > 00:00:02.781 at > jenkins.plugins.maveninfo.extractor.MavenInfoExtractor.extract(MavenInfoExtractor.java:58) > 00:00:02.781 at > jenkins.plugins.maveninfo.extractor.MavenInfoEnvironment.tearDown(MavenInfoEnvironment.java:42) > 00:00:02.781 at > hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:852) > > Happened with 1.542 so I rolledback to 1.538 and I still get the issue. > Rolling back the change gets me a working build again. The change is simply > to change an internal dependency from an old release (0.4.1) to a newer > 0.5.0-SNAPSHOT version. This is a trivial change, yet triggers the null > pointer exception. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
