Example: I have a custom shell script that does a generic task, it's populated with runtime variables that bamboo sets. Currently I have to configure this task on each project I want to execute it on.
Idea: have a global task that I could share to many projects/builds, that would pull runtime variables and execute the task
Why: If I need to update the logic of this task, I can do it once and apply to all. Currently I have to update all tasks per project
Take a look at Bamboo Specs https://confluence.atlassian.com/bamboo/bamboo-specs-894743906.html
It was designed exactly for that reason. You can keep code at repository and manage your plans from local machine or configure Bamboo to manage plans by reading code from repository
It's up to you how to organize Specs code.
For example you can have repository with plan configuration, but it's not required to keep it along with your application code if Specs is Java code.
So in your example repo B might keep Specs code which will share common tasks for several plans and then it will be applied when changes to repo B happens.
Your code in repo A is built by plans, which were created by Specs code it repo B and don't need to checkout repo B during plan execution.
Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...