Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bamboo Deployment Triggers

We are using Bamboo Version 6.4.0. We have 6 Environments in a Bamboo Deployment Plan as shown below

Env1
Env2
Env3
Env4
Env5
Env6

We want Env6 to be executed only after Env1 thru Env5 are successfully deployed.
We set the Triggers accordingly ( After Successful deployment of Env1 thru Env5).
This setup seems not working if any of the Dependent enviroments ( Env1 thru ENV5) fails.

Can someone suggest a work around for this?.

2 answers

Hi Venkat,

You can have a After Successful deployment trigger in each environment with the triggering environment being the previous environment as shown below :

If you have three environments dev, qa , prod. Configure triggers only in qa and prod with triggering environment as below :

dev <- can be triggered from bamboo plan or can be manual

qa <- dev ( triggered by dev deployment once it is success )

prod <- qa  ( triggered by qa deployment once it is success )

Do not create multiple triggers like below :

qa <- dev

prod <- dev , qa 

By doing so , prod will trigger in cases dev is successful but qa failed.

Hope this helps.

 

Regards,

Rajath

Rajath,

Thank you so much for your reply. I think you din't understand our situation.Let me explain you our situation one more time.

We have Bamboo Deployment Plan which has 6 deployment environments ( Env1 , Env2 ,Env3, Env4 , Env5 and Env6 ).

We want Env6 to deployed only if all of the depending Environments ( Env1 , Env2 ,
Env3, Env4 , Env5 ) are deployed successfully.

We setup the Triggers for Env6 accordingly ( After Successful deployment of Env1 thru Env5 ).We were expecting Env6 will be deployed only once ( when all of the Env1 thru Env5 are deployed successfully.

But the problem is sometimes Env6 is being deployed 5 times which means , Env6 is being deployed immediately after Env1 , Env2 ,Env3, Env4 , Env5 are deployed.

Venkat,

 

If Env6 is deploying five times, I guess you have given 5 triggers for it to trigger.  That is not the ideal case. If you want to trigger Env6 only after all the other environments are successful, you should follow the method like I said. 

Your method (assumption) :

Triggers in Env6 :  Env1 , Env2 ,Env3, Env4 , Env5 

This will result in triggering Env6 everytime one of the Env1 - Env5 are successful making 5 deployments for Env6

 

Correct way : 

Triggers in Env2 : Env1 

Trigger in Env3 : Env2

Trigger in Evn4 : Env3

Trigger in Env5 : Env4 

Trigger in Evn6 : Env5

This way Env6 will trigger only after all the first 5 Env are successful. Also if any of the first 5 fails it`ll stop the flow and Env1 can be triggered manually or by the bamboo plan providing artifacts to it.

 

Hope this helps.

 

Regards,

Rajath

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

251 views 4 6
Read article

Community Events

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

Events near you