Pull request to automatic plan branch creation

[Adam Clauss]

We have recently begun experimenting with enabling automatic plan branch creation when a pull request gets created.

However, we are struggling with how that then relates to multiple versions of software. Naturally, over time, we have to add/remove some aspect of our build plans.  When we hit one of these times, we currently create a new build plan as a copy of the first and make the appropriate changes to it.  We can create a linked repository that points to the appropriate branch (develop, etc) for the new version.  The old plan remains in case a patch/hotfix is needed.

However, with the pull request branch creation option enabled, now both build plans create a plan branch and run when a pull request is entered.

A more specific example: You have three branches defined:

master

develop

feature/add-something

There is a Bamboo plan pointed to master.  There is another Bamboo plan pointed to develop to build the new components being added.  A pull request then gets entered to merge the feature/add-something branch into develop.

Bamboo then creates feature/add-something plan branches in BOTH the "master" and "develop" plans.  The master one checks out the feature/add-something commit and attempts to build it, failing.

This seems like it would be a common occurrence.  How are others dealing with this type of a situation?

Thanks

[Daniel Santos]

Hi Adam,

I know this question is a bit old, but I think it worths to link relevant information here. This problem could bee solved with the implementation of the following feature request:

• [BAM-19825] Branch regular expression filter for automatic PR detection
  
  

Anyone that thinks this feature is relevant might want to vote on the above feature request to give more visibility to it.

Thanks!