We are using bamboo plan branches to do internal releases towards our testing team. E.g. there is a branch "release/tool-1.0", the next release branch will be named "release/tool-2.0" and so on...
The git branches matching the pattern "release/*" are build by a single build plan, that creates plan branches as soon as a new release branch appears.
I now got a bamboo deployment project to promote the internal releases to the testing team. Unfortunately I have to edit the deployment project every time there is a new release branch. The deployment project seems to be not aware of the plan branches feature.
So how to correctly use plan branches, without the need to manually edit the deployment project every single release?
This is how we've addressed this problem:
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
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