I fixed this bug: The Jenkins job suddenly had a wrong target machine for the build. It's now fixed to be run on the lucene slave node again.
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Apache Jenkins Server [mailto:[email protected]] > Sent: Saturday, June 07, 2014 12:11 PM > To: [email protected] > Subject: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #641: POMs out of sync > > Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/641/ > > No tests ran. > > Build Log: > [...truncated 169 lines...] > BUILD FAILED > /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven- > 4.x/build.xml:483: The following error occurred while executing this line: > /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven- > 4.x/build.xml:104: The following error occurred while executing this line: > /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven- > 4.x/lucene/build.xml:194: The following error occurred while executing this > line: > /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven- > 4.x/lucene/common-build.xml:401: The following error occurred while > executing this line: > /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven- > 4.x/lucene/common-build.xml:438: Ivy is not available > > Total time: 1 second > Build step 'Invoke Ant' marked build as failure Recording test results Email > was triggered for: Failure Sending email for trigger: Failure > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
