[BAP-189] Release Management doesn't support Shared Credentials Created: 19/Nov/13  Updated: 12/Apr/14  Resolved: 06/Apr/14

Status: Resolved
Project: Bamboo Artifactory Plug-in
Component/s: None
Affects Version/s: 1.6.1
Fix Version/s: 1.7.0

Type: Bug Priority: Blocker
Reporter: Daniel Hopper Assignee: Lior Hasson (Inactive)
Resolution: Fixed Votes: 2
Labels: release

CentOS 6.4, Bamboo 5.2.1

Attachments: JPEG File bamboo-artifactory-promotion.JPG    


When trying to perform a release via the release management after the build completes successfully and artifacts have been deployed the build will fail at the end with the following error message:

Failed to execute plugin 'Artifactory Release Management Staging' with error: java.lang.IllegalArgumentException: No enum constant org.jfrog.bamboo.release.scm.git.GitAuthenticationType.SHARED_CREDENTIALS

The repository is using the Shared Credentials feature in Bamboo 5.2

Comment by Johan Ferner [ 11/Dec/13 ]

Affects us too. Any estimated time on a fix?

Comment by Daniel Hopper [ 16/Jan/14 ]

This has become a very big blocker for us. Are there any plans to fix this? Due to a big in both Bamboo and the plugin you can't use parameters for the username/password values for repositories. Bamboo recommends using the Shared Credentials now instead as it is a better approach, but we are then unable to use the Release Management Plugin at all.

Can this feature please be added, it is now almost 2 months old.

Comment by Daniel Hopper [ 05/Feb/14 ]

It has been almost 3 months now since this has been reported and it still isn't fixed?

This is making your Release Management plugin unusable for an enterprise that is using Shared Credentials. When exactly is the plan to take this issue and fix this lacking feature.

Comment by Daniel Hopper [ 04/Mar/14 ]

What does it take to get issues like this resolved?

Comment by Wahid Atif [ 11/Apr/14 ]

Hi Lior,

I noticed that the credentials stored as global variables cannot be resolved when promoting a release.

2014-04-11 14:43:08,052 ERROR [Thread-756] [PromotionThread] Promotion failed during dry run (no change in Artifactory was done): HTTP/1.1 401 Unauthorized<br/>{
"errors" : [

Unknown macro: { "status" }


The promotion works, If I enter the credentials directly within the Artifactory Maven Task.
When running a plan (snapshot build) or staging from the Artifactory release management tab, the credentials stored as global variables can be resolved but not promoting.

Can you reproduce this?

Best Regards,

Comment by Daniel Hopper [ 11/Apr/14 ]

I just upgraded this plugin on one of our Lab instances of Bamboo running 5.4.2 and the Release and Promotion tab is missing entirely. Is there something else that needs to be reconfigured for this to work as it did previously?

Comment by Daniel Hopper [ 11/Apr/14 ]

Nevermind, looks like it was moved to a tab that is under the Build -> Stage -> Task that has the Artifactory task on it. Not a huge fan of that change as now it puts the release and promotion buried and not as easy for users to find.

Comment by Wahid Atif [ 12/Apr/14 ]

Hi Daniel,

I also noticed that and commented on the relating issue https://www.jfrog.com/jira/browse/BAP-197

Do you also have to build a SNAPSHOT version at first before you can start a release build from the release management tab?

Generated at Wed Jul 08 02:37:40 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.