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

Multiple Stages and Deployment need to happen in between stages


How to achieve the following use case with in Single plan.

Plan >>

           (Master branch) Stage 1 >> Deployment (Env Master ) >> Stage 2 >> Stage 3 

           (Feature branch) Stage 1 >> Deployment (Env Feature )>> Stage 2 >> Stage 3 




1 answer

0 votes

Hi @arun4d,

This configuration can be achieved in a Bamboo Deployment, but it is not automatic. Any environment can run separatedly and build an specific branch configured in your environment trigger. This is what you can do:

  1. Create the env master
  2. Add a trigger (After successful build plan or other) for the master branch as described here:
  3. Create the env feature
  4. Add the trigger for the feature branch as shared here: Deployments from branches - Atlassian Documentation .

If you want a different feature branch to trigger a deployment you will need to add another trigger for that branch.

Usually, environments are not defined per branch, but per virtual/physical environment where you want to deploy your code (e.g. QA, Production, etc). Multiple iterations of the application development and testing could be handled by your plan and the deployment ideally would handle the release candidates and releases or any bugfix that needs to be also released to the end user. That would not happen for all your feature branches, but for specific branches where you need to fix something and deploy.

There is a similar thread about this in this community post: Branch usage in deployment project. There you can find also a feature request that intends add the automatic deployment handing per branch. Please add your comments there and vote o that issue if that represents your needs.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events