Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

Atlassian Community Events