Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
Description
Problem Definition
As for now, it's possible to select three different variable scopes when configuring the "Version Variable Incrementer" task in Bamboo:
- Local scoped variables are only available inside the same job. Next jobs, stages, or deployments will retain the original value defined at the very beginning of the build.
- Result scope variables will be available in the current job and passed into subsequent stages or related deployment releases. Next runs will use the value defined in the plan configuration.
- Plan scoped variables will be available from the next run of the build, and it will reflect in the build configuration; it will not affect the currently running build or its deployments.
Suggested Solution
In some scenarios, it might be needed to use the updated value of the variable on later stages/jobs of the same plan (Result scope variables) and subsequent builds (Plan scoped variables). For these types of scenarios, it would be nice to be able to select multiple options at the task configuration or to have a separate option covering this requirement.
Workaround
Use the "Inject Bamboo variables" task that allows reading the current values from variables, and create new "ephemeral" build scoped variables that can be used in subsequent stages