When working with a single deployment project, what is the recommended approach to deal with hotfixes on older production branches? We are using separate build plans for each production branch, and are struggling with not being able to link multiple build plans to a single deployment project.
Production branches -> Prod-2.1, Prod-2.2, Prod-2.3
Deployment project (containing all Production and QA environments), linked to Prod-2.3
We want to update Prod-2.2 with a hotfix, and create a release from it.
The only options seem to be:
1. Use separate build plans for production branches. This would require manually switching the linked build plan whenever you want to create a release from a different branch.
2. Have all production branches as plan branches. This lets you create releases directly from multiple branches. However plan branches seem to be intended for short-lived branches, and the Build Dashboard hides their status & actions by default, which is not ideal.
Both of these options have drawbacks, and do not seem to be using the features in their intended manner.
If you are using totally separate build plans (instead of plan branches) then I think you are out of luck, because that's not the way to do things.
If however you are using Plan Branches, navigate to your deployment project, click deploy, create new release from build result, select the plan branch.
Best of luck,
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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...
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!
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