I was hoping to be able to use the `bamboo-specs` to define our plan per branch. This would allow us to have a different plan for each branch, and support branch, which makes sense as your build system and requirements evolves over time. So what is needed today might be different than what you needed six months ago which is where your support branch is. However the `bamboo-specs` is repository wide, and so every branch is built in an identical fashion.
What we have decided to do is to have a very simple build plan, that simply calls a script in our repository, and this script can evolve over time. However this is suboptimal, as it means that we cannot use different jobs to run different parts of the build in parallel.
Are there other approaches that can be taken? And what are the advantages/disadvantages of these?
G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events