org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata ****/maven-metadata.xml: Could not transfer metadata ****/maven-metadata.xml from/to ****: unknown error

Jenkins JIRA | Julien Carsique | 4 months ago
  1. 0

    [JIRA] (JENKINS-36951) Deploy artifacts to Maven repository from slave

    Google Groups | 4 months ago | jcar...@java.net (JIRA)
    org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata ****/maven-metadata.xml: Could not transfer metadata ****/maven-metadata.xml from/to ****: unknown error
  2. 0

    The build step 'Deploy artifacts to Maven repository' (RedeployPublisher) feature performs the deployments from the master. That can lead to an UnknownHostException if only the slave can access the target repository. {code}org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata ****/maven-metadata.xml: Could not transfer metadata ****/maven-metadata.xml from/to ****: unknown error at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:143) at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:193) at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:176) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1047) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) (...) Caused by: java.net.UnknownHostException: ****: unknown error {code} That can also be a network bandwidth issue if the slave has a better connection with the repository than the master. It would be great being able to choose where the artifact deployment should be performed from.

    Jenkins JIRA | 4 months ago | Julien Carsique
    org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata ****/maven-metadata.xml: Could not transfer metadata ****/maven-metadata.xml from/to ****: unknown error
  3. 0

    Our build https://builds.apache.org/job/ServiceMix-master has problems with deploying snapshots to snapshot repository using the "Deploy artifacts to Maven repository" Jenkins plugin Maven RedeployPublisher use remote jenkins-test-45d maven settings from : /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/conf/settings.xml [ERROR] uniqueVersion == false is not anymore supported in maven 3 [INFO] Deployment in https://repository.apache.org/content/repositories/snapshots (id=apache.snapshots.https,uniqueVersion=false) Deploying the main artifact activemq-7.0.0-SNAPSHOT.pom Downloading: https://repository.apache.org/content/repositories/snapshots/org/apache/servicemix/activemq/7.0.0-SNAPSHOT/maven-metadata.xml Downloaded: https://repository.apache.org/content/repositories/snapshots/org/apache/servicemix/activemq/7.0.0-SNAPSHOT/maven-metadata.xml (608 B at 28.3 KB/sec) Uploading: https://repository.apache.org/content/repositories/snapshots/org/apache/servicemix/activemq/7.0.0-SNAPSHOT/activemq-7.0.0-20160420.050305-40.pom ERROR: Failed to deploy artifacts: Could not transfer artifact org.apache.servicemix:activemq:pom:7.0.0-20160420.050305-40 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/servicemix/activemq/7.0.0-SNAPSHOT/activemq-7.0.0-20160420.050305-40.pom. Return code is: 401, ReasonPhrase: Unauthorized. org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact org.apache.servicemix:activemq:pom:7.0.0-20160420.050305-40 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/servicemix/activemq/7.0.0-SNAPSHOT/activemq-7.0.0-20160420.050305-40.pom. Return code is: 401, ReasonPhrase: Unauthorized. at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:143) at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:193) at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:176) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1047) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) See https://builds.apache.org/job/ServiceMix-master/39/console for more info.

    Apache's JIRA Issue Tracker | 8 months ago | Krzysztof Sobkowiak
    org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact org.apache.servicemix:activemq:pom:7.0.0-20160420.050305-40 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/servicemix/activemq/7.0.0-SNAPSHOT/activemq-7.0.0-20160420.050305-40.pom. Return code is: 401, ReasonPhrase: Unauthorized.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [JIRA] Created: (JENKINS-11248) Build fails on "Deploy artifacts to Maven repository" due to trying to upload parent POM twice for release artifacts

    Google Groups | 5 years ago | mrasm...@luthresearch.com (JIRA)
    org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact com.luthresearch.surveysavvy.member:surveysavvy-member:pom:0.6.2 from/to com.luthresearch (dav:http://maven.luthresearch.com/nexus/content/repositories/releases): Failed to transfer file: http://maven.luthresearch.com/nexus/content/repositories/releases/com/luthresearch/surveysavvy/member/surveysavvy-member/0.6.2/surveysavvy-member-0.6.2.pom. Return code is: 400
  6. 0

    Scenario: We have several sets of Java OSGi services with a parent pom and 4 child projects/poms. The parent pom does not generate any JARs, but each of the children generates a jar.Something like the following: {noformat} project_folder/ |_servicename.business/ | \_pom.xml |_servicename.jms/ | \_pom.xml |_servicename.model/ | \_pom.xml |_servicename.webservice/ | \_pom.xml \_pom.xml {noformat} Each of these services is setup as a separate Jenkins job, and the maven dependencies are turned on so they all build in the appropriate order. Within the parent pom we have our <distributionManagement> section defined so we can run the mvn deploy goals to upload artifacts to our maven repository. Up until this point we have only been building SNAPSHOTS, for which the Nexus repository allows redeploying of artifacts. WHAT IS GOING WRONG: The other day we tried to build our first release version of some of the services, and the deployment into the Nexus maven repository failed on the "Deploy artifacts to Maven repository" task. Looking at the Console Output of the failed job, for some reason Jenkins is trying to deploy the parent POM a second time. Nexus refuses this, as it does not allow redeploying of release artifacts. Below is an excerpt from the output of one of those jobs: {quote} [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 52.240s [INFO] Finished at: Thu Oct 06 14:55:37 GMT 2011 [INFO] Final Memory: 63M/151M [INFO] ------------------------------------------------------------------------ channel stopped Maven RedeployPublished use remote maven settings from : /opt/maven/conf/settings.xml [ERROR] uniqueVersion == false is not anymore supported in maven 3 [INFO] Deployment in dav:http://maven.luthresearch.net/nexus/content/repositories/releases/ (id=com.luthresearch,uniqueVersion=false) Deploying the main artifact savvyconnect-1.0.1.pom Uploading: dav:http://maven.luthresearch.net/nexus/content/repositories/releases/com/luthresearch/savvyconnect/savvyconnect/1.0.1/savvyconnect-1.0.1.pom Uploaded: dav:http://maven.luthresearch.net/nexus/content/repositories/releases/com/luthresearch/savvyconnect/savvyconnect/1.0.1/savvyconnect-1.0.1.pom (3 KB at 24.4 KB/sec) Uploading: http://maven.luthresearch.net/nexus/content/repositories/releases/com/luthresearch/savvyconnect/savvyconnect/1.0.1/savvyconnect-1.0.1.pom ERROR: Failed to deploy artifacts: Could not transfer artifact com.luthresearch.savvyconnect:savvyconnect:pom:1.0.1 from/to com.luthresearch (dav:http://maven.luthresearch.net/nexus/content/repositories/releases/): Failed to transfer file: http://maven.luthresearch.net/nexus/content/repositories/releases//com/luthresearch/savvyconnect/savvyconnect/1.0.1/savvyconnect-1.0.1.pom. Return code is: 400 org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact com.luthresearch.savvyconnect:savvyconnect:pom:1.0.1 from/to com.luthresearch (dav:http://maven.luthresearch.net/nexus/content/repositories/releases/): Failed to transfer file: http://maven.luthresearch.net/nexus/content/repositories/releases//com/luthresearch/savvyconnect/savvyconnect/1.0.1/savvyconnect-1.0.1.pom. Return code is: 400 at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:141) at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:189) at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:158) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:668) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:987) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:615) at hudson.model.Run.run(Run.java:1428) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:478) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: org.sonatype.aether.deployment.DeploymentException: Failed to deploy artifacts: Could not transfer artifact com.luthresearch.savvyconnect:savvyconnect:pom:1.0.1 from/to com.luthresearch (dav:http://maven.luthresearch.net/nexus/content/repositories/releases/): Failed to transfer file: http://maven.luthresearch.net/nexus/content/repositories/releases//com/luthresearch/savvyconnect/savvyconnect/1.0.1/savvyconnect-1.0.1.pom. Return code is: 400 at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:284) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:215) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:480) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) ... 11 more Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact com.luthresearch.savvyconnect:savvyconnect:pom:1.0.1 from/to com.luthresearch (dav:http://maven.luthresearch.net/nexus/content/repositories/releases/): Failed to transfer file: http://maven.luthresearch.net/nexus/content/repositories/releases//com/luthresearch/savvyconnect/savvyconnect/1.0.1/savvyconnect-1.0.1.pom. Return code is: 400 at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:949) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:940) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.flush(WagonRepositoryConnector.java:864) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:466) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:278) ... 14 more Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://maven.luthresearch.net/nexus/content/repositories/releases//com/luthresearch/savvyconnect/savvyconnect/1.0.1/savvyconnect-1.0.1.pom. Return code is: 400 at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:825) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:465) ... 15 more [INFO] Deployment failed after 0.27 sec Build step 'Deploy artifacts to Maven repository' changed build result to FAILURE Sending e-mails to: devstaff@luthresearch.com Finished: FAILURE {quote} CONFIRMATION OF ISSUE: I logged into the build server, went to the project in the Jenkins workspace, deleted the existing release artifacts from the maven repository, and manually ran the mvn deploy goal. It succeeded in uploading all of the artifacts including the JARs. WORKAROUND: I disabled the "Post-Build Actions"->"Deploy artifacts to Maven repository." I then setup a "Post Steps"->"Invoke top-level Maven target" task with the Maven goal of "deploy". (I believe this functionality is provided by the Jenkins M2 Extra Steps Plugin. https://wiki.jenkins-ci.org/display/JENKINS/M2+Extra+Steps+Plugin) Using the post build step to execute the deploy goal succeeds in successfully uploading all of the artifacts.

    Jenkins JIRA | 5 years ago | Michael Rasmussen
    org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact com.mycompany.sw.security.bsf:aum-build-cfg:pom:6.00.00_jdk_6_6 from/to MYPRODUCT_6_JDK1_6 (http://ilbldlnx07.mycompany:8081/nexus/content/repositories/MYPRODUCT_6_JDK1_6): Failed to transfer file: http://ilbldlnx07.mycompany:8081/nexus/content/repositories/MYPRODUCT_6_JDK1_6/com/mycompany/sw/security/bsf/aum-build-cfg/6.00.00_jdk_6_6/aum-build-cfg-6.00.00_jdk_6_6.pom. Return code is: 400

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.apache.maven.artifact.deployer.ArtifactDeploymentException

      Failed to retrieve remote metadata ****/maven-metadata.xml: Could not transfer metadata ****/maven-metadata.xml from/to ****: unknown error

      at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy()
    2. Maven
      DefaultArtifactDeployer.deploy
      1. org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:143)
      1 frame
    3. Legacy Maven 2 job type Plugin
      MavenArtifactRecord.deploy
      1. hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:193)
      1 frame
    4. Hudson Maven Embedder
      RedeployPublisher.perform
      1. hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:176)
      1 frame
    5. Hudson
      AbstractBuild$AbstractBuildExecution.performAllBuildSteps
      1. hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      2. hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
      3. hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)
      3 frames
    6. Hudson Maven Embedder
      MavenModuleSetBuild$MavenModuleSetBuildExecution.post2
      1. hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1047)
      1 frame
    7. Hudson
      Run.execute
      1. hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)
      2. hudson.model.Run.execute(Run.java:1763)
      2 frames
    8. Hudson Maven Embedder
      MavenModuleSetBuild.run
      1. hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
      1 frame
    9. Hudson
      Executor.run
      1. hudson.model.ResourceController.execute(ResourceController.java:98)
      2. hudson.model.Executor.run(Executor.java:410)
      2 frames