Is Bamboo suitable for deployments to multiplie client production environments.

Justin Frost August 3, 2014

We have setup bamboo for CI builds and releases. What we want to do is to deploy the releases to multiple customer production environments in the cloud (in addition to our internal testing environments also in the cloud.).

The deployment is made up of a web app (.war), database changes (.jar) and other artifacts (openRoad app server images etc).

Is Bamboo able to handle this, we could end up with over 100 environments setup for deployment.

Is there a recomended 3rd party tool to handle the deployment side of things ?

1 answer

1 accepted

1 vote
Answer accepted
Gretchen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 10, 2014

That's a tough one without knowing a bit more. If the deployable objects (wars, jars etc.) are identical you might get a good result scripting it on each customer's site to pull from a central repository (whether that is source or something like nexus or artifactory) on demand or on a cron job for example. This might have the benefit of allowing the customer to control when their deployment occurs.

Are all 100 customers expecting the deployment of new apps to occur at the same time? If not this could be a snag. What happens if the file transfers work successfully at 97 customers, but three customers fail (due to something like network issues etc. outside your control). This would make scripting it as a single deployment push script undesirable. If one or two customers don't want a particular release until a later date (due to some unforseen ridiculousness) having a single script to deploy to all customers would also be inconvenient.

Perhaps the best option would be to set up a deployment project for each customer and schedule it, or in the case of continuous deployment just deploy on successful build (or another deployment plan success). I think you can have multiple deployments from the same build (therefore pulling the same build artifacts).

That might be a pretty good solution, assuming the transfer mechanism you require and the access is available from your bamboo server. This would be kind of a nuisance to setup but I think would work pretty well and give you good visibility into what customers had successful deployments and which ones failed. (out of 100 you have to figure one or two will fail occasionally, just due to Murphy's Law).

In any case Bamboo can help with all but the first scenario.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events