Problem Definition

Bamboo currently caches global variables at the time the build that resulted in the release was executed, and if the variable values were modified after that, the changes will only take effect on the next builds/releases.

It's understandable that in some cases is important to keep the same context (to get consistent build re-runs, for example) but, it's debatable that this same logic should also be applied to global variables in deployments as they are often used to store credentials that sometimes needs to be updated.

Suggested Solution

Bamboo should allow global variables values to be read in runtime when deploying releases to environments.

Workaround

No workaround is available.