How to achieve the following use case with in Single plan.
(Master branch) Stage 1 >> Deployment (Env Master ) >> Stage 2 >> Stage 3
(Feature branch) Stage 1 >> Deployment (Env Feature )>> Stage 2 >> Stage 3
Hi @Arun Duraisamy,
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:
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.
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events