Bamboo Variable Promotion: Local Builds Succeed, Production Deployments Fail

Variable Promotion Discrepancy

In Bamboo 8.x, build‑plan variables can be promoted to deployment projects. Locally, a promoted variable is automatically available to the agent, so test builds complete without issue. When the same plan is run on a production instance, the deployment project often receives an empty value or no value at all, causing downstream failures.

The UI indicates that promotion applies to all deployments by default, yet the REST API requires each deployment project to declare the promoted variables explicitly. If a deployment environment lacks the variable declaration, Bamboo silently substitutes an empty string.

Uncertainty remains about how promoted variables are inherited by child plans or downstream pipelines, and whether a global promotion setting exists that can override the per‑project requirement.

Key Unresolved Questions

• Why do promoted variables not automatically propagate to deployment projects in production?
• What exact configuration steps are needed to ensure promoted variables reach all deployment environments?
• Is there a documented difference between Bamboo’s UI promotion defaults and the API’s per‑project declaration requirement?