[HAP-534] Artifactory release Promotion fails when 'Include dependencies' was checked once Created: 22/Oct/14  Updated: 14/Nov/17  Resolved: 23/Aug/15

Status: Resolved
Project: Jenkins Artifactory Plug-in
Component/s: None
Affects Version/s: 2.3.1
Fix Version/s: 2.4.0

Type: Bug Priority: Normal
Reporter: Ariel Seftel Assignee: Lior Hasson (Inactive)
Resolution: Fixed Votes: 1
Labels: None

Attachments: JPEG File ReleasePromotion.JPG    
Issue Links:
Relationship
is related to HAP-396 Moving artifacts residing in multiple... Resolved

 Description   

When doing 'Artifactory Release Promotion' with 'Include dependencies' on Maven job, and the user does not have the permission to move the dependency, an error of lack of permissions is shown. That is a normal behavior but the issue is when trying to run 'Artifactory Release Promotion' right after without the 'Include dependencies' than it fails with the same error of lacking permission to delete the dependency.
Scenario to reproduce:
1. Run a build.
2. Run Artifactory Release Staging.
3. Run Artifactory Release Promotion with Include dependencies checked when the dependency is deployed to a repository that the user does not have delete permission on.
4. Run Artifactory Release Promotion without checking the Include dependencies check box.
The permission error will appear.



 Comments   
Comment by Lior Hasson (Inactive) [ 09/Aug/15 ]

A new field named " Source promotion repository" added to the promotion page in Jenkins plugin, that will recommend to Artifactory from where to look up the artifacts.

Generated at Sun Oct 20 01:03:34 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.