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

Resolve Artifacts Not Consistant

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: 3 - High
    • Resolution: Unresolved
    • Affects Version/s: 3.2.3
    • Fix Version/s: None
    • Component/s: Maven3
    • Environment:

      Jenkins 2.7.4

      maven-plugin

      artifactory-plugin

      Description

      I'm attempting to use the Resolve artifacts from Artifactory option to manage my release, however when using the 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.
       
      Pre-Steps
      n/a

      Build

      • 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

      Resolve artifacts from Artifactory seems to work throughout 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.

      Can you advise whether this is a mistake on our end, or indeed a bug as we have anticipated.

        Attachments

          Activity

            People

            Assignee:
            eyalb Eyal Ben Moshe
            Reporter:
            will_crewe Will Crewe
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: