I've commented out export PATH=/opt/subversion-1.4.0/bin:$PATH from the job configuration. This is not the right version of svn for all hudson machines. Let the defaults take over. These 2 builds revealed only a problem with svn being used, not sure if it was related to your plugin. Paul Gier wrote: > I recently added configuration of the buildnumber-maven-plugin [1] to > the AS trunk build to retrieve the current svn revision number, so > that it can be recorded in the jars. This plugin seems to be causing > failures on some Hudson instances. It ran fine in build 356, but then > failed in build 357 and 358 [3]. > > Is there someone who can look into the Hudson setup? I will look into > configuring the plugin so that it doesn't fail the build, but if > that's not possible, I will remove the use of this plugin. > > [1]http://mojo.codehaus.org/buildnumber-maven-plugin/ > [2]http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x/356/c... > > [3]http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x/358/c... > >