Smarter Bamboo CI branch building. Edited

Let me explain my problem.

 

We have a codebase that recently moved to a new version of Visual Studio.  At this time our develop git code moved, we created a new bamboo plan to build this code.   At the same time, we also created a branch old the code for the old compiler (which we still have to support occasionally), and moved the existing build plan to build that legacy code branch.

 

We use JIRA to checkout our branches, so all our branches have a JIRA key in them, and this is our trigger in our Bamboo branch creation.  The problem is, if someone branches from the old legacy code, it's detected by the bamboo CI plan, and tries to build it (and fails).  All our bramches, regardless of where is was branches from have the same JIRA project key (which I guess is the nub of the problem)

 

Is there any way of working out base branch in the CI bamboo logic?  So branches that have base branch A are built using plan A  and branches that have base branch B are built using plan B?  I think that is the  essence of my question?  

0 answers

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,066 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot