[BAP-212] Artifactory Maven task doesn't support variables anymore for deployer configuration Created: 02/Jul/14  Updated: 03/Aug/14  Resolved: 28/Jul/14

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

Type: Bug Priority: Blocker
Reporter: Daniel Hopper Assignee: Eyal Ben Moshe (Inactive)
Resolution: Fixed Votes: 1
Labels: None

Bamboo 5.5.1

Issue Links:
relates to BAP-217 Variable deployer credentials are not... Resolved
BAP-217 Variable deployer credentials are not... Sub-task Resolved  


We use global variables for the deployer username and password when configuring the Bamboo build plans for the Maven Artifactory tasks, and we just recently upgrade to Bamboo 5.5.1 and the JFrog plugin 1.7.2

It seems this is no longer support and users are getting 401 authentication issues when trying to select the target repository. This is a HUGE blocker for us as we have over 180 build plans that leverage this.

This needs to be fixed ASAP

Comment by Eyal Ben Moshe (Inactive) [ 03/Jul/14 ]

The issue has been reproduced.
Working to fix it.

Comment by Eyal Ben Moshe (Inactive) [ 03/Jul/14 ]

We created a snapshot for this fix:


Comment by Wahid Atif [ 29/Jul/14 ]

Hi Eyal,

just a short note: I've just tested the fix and it seems to work, but I had to delete the previous connection to the Artifactory server and recreate it (addon config). After that I had also to re-link it within every Artifactory task configuration, because the new connection configuration record got a new ID.


Generated at Mon Jun 01 20:40:00 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.