[BAP-182] Release plugin doesn't replace Bamboo variables Created: 15/Oct/13  Updated: 27/Nov/13  Resolved: 24/Nov/13

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

Type: Bug Priority: Critical
Reporter: Daniel Hopper Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

Linux, Bamboo 5.0.1



 Description   

When attempting to use the Release portion of the Bamboo plugin we discovered that it doesn't support Global variables. We have our repositories configured with variables that don't get replaced and thus we get an access denied.

simple	15-Oct-2013 08:21:05	[RELEASE] Pushing branch: release/1.0.0 to url: http://${bamboo.stash.domain}/scm/commons/framework.git
error	15-Oct-2013 08:21:05	[RELEASE] An error 'http://${bamboo.stash.domain}/scm/commons/framework.git: cannot open git-receive-pack' occurred while pushing branch: release/1.0.0 to url: http://${bamboo.stash.domain}/scm/commons/framework.git
simple	15-Oct-2013 08:21:05	[RELEASE] Checking out branch: master
simple	15-Oct-2013 08:21:05	[RELEASE] Deleting local branch: release/1.0.0
simple	15-Oct-2013 08:21:05	[RELEASE] Deleting local tag: 1.0.0
simple	15-Oct-2013 08:21:05	[RELEASE] Reverting local copy to: de1523f8aa4331e387ecc1703b31548c96c0e7d0
error	15-Oct-2013 08:21:05	Failed to execute plugin 'Artifactory Release Management Staging' with error: java.io.IOException: An error 'http://${bamboo.stash.domain}/scm/commons/framework.git: cannot open git-receive-pack' occurred while pushing branch: release/1.0.0 to url: http://${bamboo.stash.domain}/scm/commons/framework.git

To fix this I had to switch out all the variables with the hard coded values for it to work.



 Comments   
Comment by Daniel Hopper [ 19/Nov/13 ]

Any movement on this? This is quite a large issue for us as we have hundreds of repositories that are configured this way making this feature completely unusable.

Comment by Daniel Hopper [ 27/Nov/13 ]

While this fixes the replace of values in the domain, it doesn't work for username or password fields. Those still appear to not get replace as I will get not authorized errors unless I put in the specific username/password.

Values like

${bamboo.stash.username}
${bamboo.stash.password}

with globally configured variables will fail.

Generated at Thu Aug 22 05:29:50 UTC 2019 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.