[EnvInject] - Loading node environment variables. Building remotely on Common in workspace /opt/projects/jenkins/workspace/Common-jboss-build-InboundWebServicesOracleEDWDB@2 Checking out a fresh workspace because there's no workspace at /opt/projects/jenkins/workspace/Common-jboss-build-InboundWebServicesOracleEDWDB@2 Cleaning local Directory .
[JENKINS] Archiving /opt/projects/jenkins/workspace/Common-jboss-build-InboundWebServicesOracleEDWDB@2/pom.xml to com.centene.mms.trucare/InboundWebServicesOracleEDWDB/0.0.1-SNAPSHOT/InboundWebServicesOracleEDWDB-0.0.1-SNAPSHOT.pom [JENKINS] Archiving /opt/projects/jenkins/workspace/Common-jboss-build-InboundWebServicesOracleEDWDB@2/target/InboundWebServicesOracleEDWDB.war to com.centene.mms.trucare/InboundWebServicesOracleEDWDB/0.0.1-SNAPSHOT/InboundWebServicesOracleEDWDB-0.0.1-SNAPSHOT.war ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com java.lang.NullPointerException at java.util.StringTokenizer.<init>(StringTokenizer.java:182) at java.util.StringTokenizer.<init>(StringTokenizer.java:219) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:326) at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:175) at hudson.tasks.MailSender.getMail(MailSender.java:166) at hudson.tasks.MailSender.execute(MailSender.java:100) at hudson.maven.reporters.MavenMailer.end(MavenMailer.java:56) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:103) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:829) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1670) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) project=hudson.maven.MavenModuleSet@5777e6c[Common-jboss-build-InboundWebServicesOracleEDWDB] project.getModules()=[hudson.maven.MavenModule@7bc70b96[Common-jboss-build-InboundWebServicesOracleEDWDB/com.centene.mms.trucare:InboundWebServicesOracleEDWDB][Common-jboss-build-InboundWebServicesOracleEDWDB/com.centene.mms.trucare:InboundWebServicesOracleEDWDB][relativePath:]] project.getRootModule()=hudson.maven.MavenModule@7bc70b96[Common-jboss-build-InboundWebServicesOracleEDWDB/com.centene.mms.trucare:InboundWebServicesOracleEDWDB][Common-jboss-build-InboundWebServicesOracleEDWDB/com.centene.mms.trucare:InboundWebServicesOracleEDWDB][relativePath:] FATAL: null java.lang.NullPointerException at java.util.StringTokenizer.<init>(StringTokenizer.java:182) at java.util.StringTokenizer.<init>(StringTokenizer.java:219) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:326) at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:175) at hudson.tasks.MailSender.getMail(MailSender.java:166) at hudson.tasks.MailSender.execute(MailSender.java:100) at hudson.maven.reporters.MavenMailer.end(MavenMailer.java:56) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:103) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:829) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1670) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231)
I am wondering what is causing the Jenkins to create the extra workspace with the "@" in the name.
Looking at the job config history, it looks like the user SYSTEM made a configuration change to set the Throttle concurrent build plugin to have the value 1 for configVersion. Is this what is or was causing this secondary workspace to be created? Also I am trying to figure out why the system user is listed as the one making some of these changes. Even with this no longer being defined in the job, it is now building with the workspace that has the "@2" appended to the name.
Thanks.
We are running an older version of Jenkins (1.548) and we do have plans in place to get our version up to one of the more recent versions, we just have to make sure that since there are at least two major updates with regards to Jenkins (java version and another that would be difficult to backout from easily) that we are going to have to go about it in at least 2-3 phases.
ThanksMatthew