kutzi
added a comment - 16/Aug/11 2:40 PM 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

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

One workaround/fix is to take maven-plugin.hpi from a recent Jenkins-on-Jenkins build. I'm actually running my own build of maven-plugin.hpi based off of commit 5c7184d3cdccde44eaf8d73a38151a1c6ee5f9a9 for the past 24 hours with no ill effects.

Richard Mortimer
added a comment - 18/Aug/11 10:26 PM One workaround/fix is to take maven-plugin.hpi from a recent Jenkins-on-Jenkins build. I'm actually running my own build of maven-plugin.hpi based off of commit 5c7184d3cdccde44eaf8d73a38151a1c6ee5f9a9 for the past 24 hours with no ill effects.
That should be the same as the build done at
http://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_main_trunk/1056/
The appropriate plugin would be
http://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_main_trunk/1056/artifact/maven-plugin/target/maven-plugin.hpi
Of course you will have to remember to unpin that version when you get the official 1.427 build.
YMMV but it is one option available.

I'm still seeing this error with 1.427 running on Ubuntu 10.04. This is a blocker since we use Jenkins with the Gerrit Trigger plugin which results in all our jobs being marked as failed even though the build finishes successfully.

Diwaker Gupta
added a comment - 19/Aug/11 6:33 PM I'm still seeing this error with 1.427 running on Ubuntu 10.04. This is a blocker since we use Jenkins with the Gerrit Trigger plugin which results in all our jobs being marked as failed even though the build finishes successfully.

I got this issue after upgrading to the Jenkins CI 1.427 and Maven 2 Plugin 1.426 (which was the one offered to me by the Update Center). I solved it by downgrading to the previously installed version of the Maven 2 plugin. When you refer to 1.427, are you talking about the M2 plugin or about Jenkins?

Richard Eckart de Castilho
added a comment - 20/Aug/11 7:57 AM I got this issue after upgrading to the Jenkins CI 1.427 and Maven 2 Plugin 1.426 (which was the one offered to me by the Update Center). I solved it by downgrading to the previously installed version of the Maven 2 plugin. When you refer to 1.427, are you talking about the M2 plugin or about Jenkins?

It looks like Maven 2 Plugin 1.427 has not been released via the update centre. However I just upgraded my jenkins to 1.427 and confirmed that 1.427 is bundled in with that. You should be able to force jenkins to use that by going to "Manage Jenkins" -> "Manage Plugins" -> "Installed" and untick "pinned" for the Maven 2 Plugin. Then when you restart jenkins it will use the plugin bundled with Jenkins.

Richard Mortimer
added a comment - 20/Aug/11 9:22 AM It looks like Maven 2 Plugin 1.427 has not been released via the update centre. However I just upgraded my jenkins to 1.427 and confirmed that 1.427 is bundled in with that. You should be able to force jenkins to use that by going to "Manage Jenkins" -> "Manage Plugins" -> "Installed" and untick "pinned" for the Maven 2 Plugin. Then when you restart jenkins it will use the plugin bundled with Jenkins.