Oddly this is still not mentioned in the Bamboo variables documentation, but you can achieve this by adding a 'Password' suffix to sensitive variables (I think at least 'Secret' works too meanwhile, there may be a few more).
For example, if the variable key is "password", "awsAccessKeyPassword", or "awsSecretKeyPassword", the build log will show the substituted variable value as "********".
A super-hacky way to do it could be to create a second global variable. So if the global variable you want to mask is:
Then you could create another global variable named, say
and make its value the same as the value of the original.
Since Bamboo only really obscures the value of the variable in all cases where it finds it in log output, as long as the same string is the value of a variable that includes PASSWORD (or SECRET), then that works.
Incidentally, in a CI environment, we have a username/password combo for a local Oracle image set to oracle/oracle. Which means any time the literal 'oracle' appears anywhere in the logs, it is obscured with a bunch of *******. And if you have to use anything oracle related, and java related, well, you get a lot of ******** in the logs :)
G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events