Uploaded image for project: 'Jenkins Artifactory Plug-in'
  1. Jenkins Artifactory Plug-in
  2. HAP-93

Hudson Release Plugin and Artifactory Plugin

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 1.3.1
    • Fix Version/s: 1.3.5
    • Component/s: Maven2
    • Labels:
      None

      Description

      Currently running into an issue with how the artifactory plugin is working when performing a release in Hudson using the maven release plugin (http://wiki.hudson-ci.org/display/HUDSON/M2+Release+Plugin). The problem occurs at the end of the release when it is trying to publish the new snapshot to artifactory. For some reason the artifactory plugin things it is working with the old snapshot version and won't let the artifact be put into artifactory. Here is the relevant log entry on hudson.

      Deploying artifacts to http://artifactory-repo:8081
      Deploying artifacts of module: groupid:artifactid
      Deploying artifact: http://artifactory-repo:8081/local-snapshots/groupid/artifactid/0.0.7-SNAPSHOT/artifactid-0.0.7-SNAPSHOT.pom
      ERROR: Failed to deploy file: HTTP response code: 404. HTTP response message: The target deployment path 'groupid/artifactid/0.0.7-SNAPSHOT/artifactid-0.0.7-SNAPSHOT.pom' does not match the POM's expected path prefix 'groupid/artifactid/0.0.8-SNAPSHOT'. Please verify your POM content for correctness and make sure the source path is a valid Maven 2 repository root path.
      java.io.IOException: Failed to deploy file: HTTP response code: 404. HTTP response message: The target deployment path 'groupid/artifactid/0.0.7-SNAPSHOT/artifactid-0.0.7-SNAPSHOT.pom' does not match the POM's expected path prefix 'groupid/artifactid/0.0.8-SNAPSHOT'. Please verify your POM content for correctness and make sure the source path is a valid Maven 2 repository root path.
      	at org.jfrog.build.client.ArtifactoryBuildInfoClient.throwHttpIOException(ArtifactoryBuildInfoClient.java:441)
      	at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:374)
      	at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:275)
      	at org.jfrog.hudson.maven2.ArtifactsDeployer.deployArtifact(ArtifactsDeployer.java:125)
      	at org.jfrog.hudson.maven2.ArtifactsDeployer.deploy(ArtifactsDeployer.java:89)
      	at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:177)
      	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:595)
      	at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
      	at hudson.model.Run.run(Run.java:1303)
      	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:293)
      	at hudson.model.ResourceController.execute(ResourceController.java:88)
      	at hudson.model.Executor.run(Executor.java:137)
      Skipping sonar analysis due to bad build status FAILURE
      Finished: FAILURE
      

      artifactory-repo, groupid, and artifactid are replacements for non-public domain information.

        Attachments

          Activity

            People

            • Assignee:
              cohen.tomer Tomer Cohen
              Reporter:
              shawnclark Shawn Clark
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: