Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-57384

Artifactory Plugin Bug - Resolve Artifacts Not Consistant


    • Similar Issues:


      I'm attempting to use the Resolve artifacts from Artifactory option to manage my release, however when using a Invoke top-level Maven targets post-build step. the Maven opperation is defaulting to using the local maven release, rather than the one selected in Artifactory.


      I'm using a Maven Project.

      Under the Build Environment tab, I'm attempting to use the Resolve Artifacts from Artifactory option for my maven release. 

      • This parses the POM during the Build and successfully interacts as we'd expect


      My entire build is as follows.





      • Goals and options: help:evaluate -Dexpression=project.version -l version.log
      • Maven Validation Level: LEVEL_MAVEN_3_1
      • Settings file: Use default maven settings
      • Global Settings file: Use default global settings

      Post Steps

      Execute Shell

      • Used to tag our git branch using the maven version.

      Invoke top-level Maven targets

      • Maven Version: localmaven (Note, there is no option to select the earlier Artifactory release, and using (default) provides the following error:
        • FATAL: command execution failed
          java.io.IOException: Cannot run program "mvn" (in directory "{DIRECTORY_PATH}"): error=2, No such file or directory
      • Goals: verify
      • Settings file: Use default maven settings
      • Global Settings file: Use default maven global settings




      My Build Resolve artifacts from Artifactory seems to work through the Build, however has no effect on the Invoke top-level Maven targets post-build step where we still wish to resolve our release using artifactory.

      This appears to be either a bug or an oversight. 



          There are no comments yet on this issue.


            • Assignee:
              eyalbe Eyal Ben Moshe
              will_crewe Will Crewe
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: