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

There is no way to manually promote an Artifactory artifact using jenkins pipeline

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • artifactory-plugin
    • None
    • Linux
      Jenkins v2.189
      Artifactory Plugin v3.3.2
      Pipeline Plugin v2.6

      We have been using the Artifactory plugin in Jenkins for many years with traditional freestyle jobs, but we are now migrating our production builds to use the new Jenkins Pipeline build scripts.

      One of the features many of our teams depend upon in the freestyle jobs is the ability to "promote" a build from one Artifactory repo to another. This feature appears as a simple check-box in the traditional freestyle jobs to enable build promotion support. When a build completes and artifacts are published, a link/button appears on the Jenkins build info page that allows the artifacts published by that build to be promoted (ie: copied to an alternative Artifactory repo). I can not find any examples or mention of this feature in the docs for the pipeline build scripts.

      There are some examples that demonstrate how we could automate the promotion process like the example project found here:

      https://github.com/jfrog/project-examples/blob/master/jenkins-examples/pipeline-examples/scripted-examples/promotion-example/Jenkinsfile

      However, we can't automate the promotion process for many of our projects. Manual processes are required to vet a build before it can be deemed releaseable. As such we need to incorporate the same manual promotion operation that used to exist in the freestyle jobs with our new pipeline based jobs.

      NOTE: If this feature is already supported by the Artifactory plugin feel free to clarify and provide an example of how this can be done.

            eyalbe Eyal Ben Moshe
            leedega Kevin Phillips
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: