We're using Hudson 1.362 with Maven 2.2.0 and Nexus 1.7.2
My problem is that without any recognizable pattern, the deployment of the built artifacts fails sometimes. For instance:
Deploying the main artifact dms-transport-frontend-1.1.0-SNAPSHOT.jar
[INFO ] Retrieving previous build number from internal.snapshots
[INFO ] Retrieving previous metadata from internal.snapshots
[INFO ] Uploading repository metadata for: 'snapshot ch.ipi:dms-transport-frontend:1.1.0-SNAPSHOT'
[INFO ] Uploading project information for dms-transport-frontend 1.1.0-SNAPSHOT
[INFO ] Retrieving previous metadata from internal.snapshots
[INFO ] Uploading repository metadata for: 'artifact ch.ipi:dms-transport-frontend'
ERROR: Error installing artifact's metadata: Error while deploying metadata: Resource to deploy not found: File: http://repository.ipie.ch/content/repositories/snapshots/ch/ipi/dms-transport-frontend/maven-metadata.xml.sha1 does not exist
org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error installing artifact's metadata: Error while deploying metadata: Resource to deploy not found: File: http://repository.ipie.ch/content/repositories/snapshots/ch/ipi/dms-transport-frontend/maven-metadata.xml.sha1 does not exist
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:102)
at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:119)
at hudson.maven.reporters.MavenAggregatedArtifactRecord.deploy(MavenAggregatedArtifactRecord.java:79)
at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:109)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601)
at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:598)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
at hudson.model.Run.run(Run.java:1276)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:124)
Caused by: org.apache.maven.artifact.repository.metadata.RepositoryMetadataDeploymentException: Error while deploying metadata: Resource to deploy not found: File: http://repository.ipie.ch/content/repositories/snapshots/ch/ipi/dms-transport-frontend/maven-metadata.xml.sha1 does not exist
at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:450)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86)
... 12 more
Caused by: org.apache.maven.wagon.TransferFailedException: Resource to deploy not found: File: http://repository.ipie.ch/content/repositories/snapshots/ch/ipi/dms-transport-frontend/maven-metadata.xml.sha1 does not exist
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:283)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifactMetadata(DefaultWagonManager.java:169)
at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:446)
... 13 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: File: http://repository.ipie.ch/content/repositories/snapshots/ch/ipi/dms-transport-frontend/maven-metadata.xml.sha1 does not exist
at org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(LightweightHttpWagon.java:168)
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:266)
... 15 more
A bit later, I start the same job again, and normally, the deployment works.
Has anyone experienced this error?
Best regards,
Eric
first you should really update to Maven 2.2.1 as the previous versions AFAIR all had severe deployment related bugs. But nothing related to your specific problem, I think.
Then I've stopped to use the 'deploy artifacts' feature of Hudson itself and using the deploy goal of Maven, because of errors like this.
This Hudson feature seems to quite buggy.
Christoph
-------- Original-Nachricht --------
> Datum: Wed, 12 Jan 2011 02:43:35 -0800 (PST)
> Von: jcrouvi <jcr...@yahoo.com>
> An: Hudson Users <hudson...@googlegroups.com>
> CC: jean-claud...@ipi.ch
> Betreff: Hudson fails to deploy from time to time