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 builds from different branches

Deleted user Aug 17, 2018

We are currently using Bamboo to deploy code from our Master branch to our environments; DEV, UAT, Staging and Production. This can cause some issues where some deployments become queued behind others.

To overcome this, we want to push from Feature branch --> QA branch, which triggers a build that is deployed to the DEV & UAT environments. This is then tested by the QA team and once signed off, we would merge the Feature branch --> Master, which then generates a new set of code/engines which we can then push to Staging and Production.

Is this possible and if so, is there an idiots guide?

1 answer

0 votes
Deleted user Oct 05, 2018

Figured this out after using the Create Plan Branch pointing to the required branch.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events