-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.420 (also experienced on 1.421) in Apache Tomcat 6.0.32
$ /home/jenkins/apache-maven-3.0.3/bin/mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600)
Maven home: /home/jenkins/apache-maven-3.0.3
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /home/jenkins/jdk1.6.0_26-x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.18-238.el5", arch: "amd64", family: "unix"
$ /home/jenkins/jdk1.6.0_26-x86_64/bin/java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
$ uname -srvmpio
Linux 2.6.18-238.el5 #1 SMP Thu Jan 13 15:51:15 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/redhat-release
CentOS release 5.6 (Final)Jenkins 1.420 (also experienced on 1.421) in Apache Tomcat 6.0.32 $ /home/jenkins/apache-maven-3.0.3/bin/mvn --version Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600) Maven home: /home/jenkins/apache-maven-3.0.3 Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: /home/jenkins/jdk1.6.0_26-x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.18-238.el5", arch: "amd64", family: "unix" $ /home/jenkins/jdk1.6.0_26-x86_64/bin/java -version java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) $ uname -srvmpio Linux 2.6.18-238.el5 #1 SMP Thu Jan 13 15:51:15 EST 2011 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/redhat-release CentOS release 5.6 (Final)
Builds for Maven based jobs are finished with "ABORTED". The build for the job appeared to work fine, and then one build would finish with "ABORTED", and all subsequent builds would do the same, even after restarting Jenkins/Tomcat. The relevant error in the logs and the console output can be found in this github gist: https://gist.github.com/1096289
The way I have been getting around this is to clear my local maven repository (rm -rf /home/jenkins/.m2/repository) (I'm not sure if this step is necessary), clearing the $JENKINS_HOME (rm -rf /home/jenkins/.jenkins), and starting with a fresh deployment of Jenkins in Tomcat. Deleting and recreating the job (with identical settings) does not solve the problem either.
The only other references to this error are a Jenkins JIRA ticket and a thread in the mailing list.
https://issues.jenkins-ci.org/browse/JENKINS-8827
http://jenkins.361315.n4.nabble.com/jenkins-maven-build-job-didn-t-get-executed-tt3457622.html
I created this issue at the user jieryn on Jenkin's IRC channel on freenode (#jenkins @ chat.freenode.net)'s request.
This particular Jenkins setup does not have any slaves.
