-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins Master 2.32.3
Artifactory-plugin 2.10.3 (upgraded from 2.9.2)
Using Gradle
After upgrading to 2.10.3, running the Artifactory Release Staging step to release a JAR into our release repo in artifactory behaves in a broken manner. Regardless of the repo chosen (Repository for release staging), the artifact is uploaded to the default SNAPSHOT repo.
Steps:
- Start Artifactory Release Staging
- On the page that appears, change the Repository for release staging. (ours is auto populated to the Release repo in the Release Management settings of the job config, SNAPSHOT repo is specified as the "publishing repository" in job config and works fine for regular builds)
- Examine build output, notice that the artifact was uploaded to the SNAPSHOT repo, ignoring specified Release Staging repo
After downgrading plugin to 2.9.2, the expected behavior was restored for us. This is our work around for now.
We fixed the issue. Here is the link to the commit:
https://github.com/JFrogDev/jenkins-artifactory-plugin/commit/1ee172b7b34b9730b51898187fda1eec174a45ce
Here is a download link for a snapshot version which includes the fix:
https://oss.jfrog.org/oss-snapshot-local/org/jenkins-ci/plugins/artifactory/2.10.4-SNAPSHOT/artifactory-2.10.4-20170424.150812-7.hpi
We would appreciate your feedback for it.