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

How to queue deployment jobs for multiple environments at once Edited

Hi,

Our application is single tenant. This lead to many application server instances as every client has its own.

We have one bamboo "Environment" per application server instance.

These are regrouped under "Deployment projects".

How can we ask Bamboo to deploy a given release to all the environments of a "Deployment Project" without having to click each of them one by one ?

I am not asking how to run multiple jobs in parallel, I know the answer is more agents.

What I want is to "queue" all the jobs with one click.

I was looking for a deploy button at the deployment project level but can not find it.

 

Thanks !

1 answer

1 accepted

0 votes
Answer accepted

You can workaround this problem using "After successful deployment" trigger:

- create a dummy environment, named for example 'All servers', make it do nothing  (for instance single script task with nothing but 'exit 0' in it)

- add After successful deployment trigger to all other environments and point to 'All servers' environment

Now whenever you deploy 'All servers', all the other environments will be triggered.

 

BTW: if you manage a big number of deployment environments perhaps you should consider using Bamboo Specs.

Thanks, I did not knew about Bamboo Specs.

A limitation of the trigger solution is that it does not allow to select the release, it will create a release from the last built.

But this could work in most cases.

 

Thanks!

>A limitation of the trigger solution is that it does not allow to select the release, it will create a release from the last built.

Actually, no, in case of this trigger, he same release that was deployed to 'parent' env is deployed to 'child' env. So you would create release once, when deploying the dummy environment and the it should propagate to all envs.

OK thanks,

 

it is this text in the trigger form which confused me:

 

Set triggers to specify how and when the deployment will be triggered automatically. When a deployment is automatically triggered, a new release is created from the latest successful build result of the linked plan. 

@Marcin Gardias  So this setup will run environment parallel or sequentially ?

Depends on number of available agents, but, in principle, it will be parallel.

@Marcin Gardias  Is there possible to run sequentially? If so, please share the details.

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 ...

250 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