Hi Steve,

could this be caused by the user name change from hudson to jenkins? I copied 
~/.m2 but maybe there is missing something.

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: Monday, August 25, 2014 11:50 AM
> To: [email protected]
> Subject: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #684: POMs out of sync
> 
> Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/684/
> 
> No tests ran.
> 
> Build Log:
> [...truncated 25266 lines...]
> BUILD FAILED
> /usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-
> 4.x/build.xml:501: The following error occurred while executing this line:
> /usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-
> 4.x/build.xml:174: The following error occurred while executing this line:
> /usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-
> 4.x/lucene/build.xml:492: The following error occurred while executing this
> line:
> /usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-
> 4.x/lucene/common-build.xml:581: Error deploying artifact
> 'org.apache.lucene:lucene-solr-grandparent:pom': Error retrieving previous
> build number for artifact 'org.apache.lucene:lucene-solr-grandparent:pom':
> repository metadata for: 'snapshot org.apache.lucene:lucene-solr-
> grandparent:4.11.0-SNAPSHOT' could not be retrieved from repository:
> apache.snapshots.https due to an error: Error transferring file: Server
> returned HTTP response code: 502 for URL:
> https://repository.apache.org/content/repositories/snapshots/org/apache/l
> ucene/lucene-solr-grandparent/4.11.0-SNAPSHOT/maven-metadata.xml
> 
> Total time: 14 minutes 7 seconds
> 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]

Reply via email to