Our release process looks like this:
This approach works fine, but we get a lot of cloned Bamboo plans (one for each release). So I'm wondering what other people are doing and what the best practice is for handling release branches and release tags in Bamboo.
Our release process is a bit rigorous, so running the plan on trunk and calling that a release is not acceptable.
Assuming that your Bamboo is recent enough, you can use the Plan Branches feature. In this way, you can use the same plan definition for multiple branches and tags.
How 'pleasant' is the Plan Branches to work with? I feel some of the features in Bamboo are clunky to work with, but if this feature is well integrated it might just solve this problem.
We don't have a recent Bamboo, but I will tell IT to upgrade.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How 'pleasant' is the Plan Branches to work with?
Don't ask me :-) I am one of the guys who developed that feature - of course I'll always tell you it's easy to use and pleasant ;-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.