You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am implementing a CI project in bamboo using git / bitbucket / jira.
At the moment, I am trying to fit everything into one plan for building my project, handling release candidate, deployments etc.
I couldn't find any concrete example of how to implement a gitflow strategy in bamboo using plans, branching features, etc and would be great if I can have any pointers?
I did not want to have multiple plans because of maintenance but perhaps I would feel different about it if there was some kind of best practices around it which I am not able to find.
Could someone share their experience or what would be the best practices regarding bamboo plans?
What I've done in the past
NOTE: any build artifact could be deployed to any environment, also we have dedicated QA and UAT teams for different environments