Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How many plans are needed to handle standard gitflow branching strategy?

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? 

1 answer

What I've done in the past


  • 1 plan to build all branches
    • if master branch, checkout latest tag, then build
  • depending on how many environments you have, set up each one to have it's own deployment
    • DEV environment, this will auto deploy any successful develop branch builds
    • QA environment, this will auto deploy any successful release* branch builds
      • to deploy the correct release branch we had to manually update the trigger to auto deploy the correct release
      • NOTE: we removed the trigger that would auto deploy on successful build and manually did the release, we found this to be easier but it's not CI/CD
    • PILOT/BETA environment, this will auto deploy any successful master branch builds
      • NOTE: since on the build we checkout the latest tag we need to rebuild the master branch after we push a new tag
    • PROD environment, this is a manual deployment so we can deploy the correct build/tag/etc... 

NOTE: any build artifact could be deployed to any environment, also we have dedicated QA and UAT teams for different environments

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events