Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best practice for when build plans need to be different per branch?

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?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo Data Center on Kubernetes

Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...

46 views 0 3
Read article

Community Events

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

Events near you