-
Suggestion
-
Resolution: Done
I have several build jobs that all share the same build invocation that contains several variables that are build agent capabilities. Whenever this invocation changes, I have to go and edit the many jobs that use it.
What I would like to be able to do is defined the build invocation as a single global variable, that itself uses variables that are capabilities of the build agent. This would allow me to define the invocation in one place which would simplify maintenance.
Another alternative would be to introduce build invocation templates that can be shared among jobs (across different plans). These templates could themselves have variables that could be unique to the job that must be configured there, which would allow the common parts of the invocation to be defined centrally yet still facilitate differences per job.
- duplicates
-
BAM-14381 embedded variables not working
-
- Closed
-
-
BAM-1315 System Variables in Bamboo should be able to reference themselves
- Closed
-
BAM-12403 Allow nested variables
- Closed
- relates to
-
BAM-13140 Add description field to each global variable on the UI
- Closed
- copied to
-
BDEV-1064 Failed to load
- is related to
-
BDEV-13743 Loading...
-
AMKTHELP-8894 Loading...
- links to
Hello guys, we are releasing this feature in version 6.3. The EAP is out if you want check it out. You can grab it here. Just go to the Bamboo variables page to learn how to use it.
If you need more information about EAP release you can find this page useful, but note EAP release notes doesn't include information about this feature.