Manual stages in bamboo 5 deploy plans

[Russell Moore]

pre-5.0 we had deployment stages as part of our build plans. With 5, having shared artifacts is nice, but maybe I'm missing something on the deploy plans - no stages, and no way to make steps manual?

here is the scenario: deploying to the produciton environment pushes an ear artifact out to several physical hosts with instances of jboss on each. What we have done in the past is to push to a single host to do smoke testing live in producion before copying the ear to all servers. This minimizes exposure to issues should there be a production-specific problem.

How we had this set up before was a stage for the first server - push the ear, restart jboss with the new ear in place, and pause. Once testers were done validating against the single server, we would resume and deploy across the rest of the server cluster.

I don't see a way to do this, except to maybe define them as different environments completely? which means a human error could cause different artifacts to be deployed across the same environment.

[Jason Monsorno · Accepted solution]

As of 5.0.1 (newest released to date) the Deployments have a single non-concurrent/syncronize workflow per environment. A workaround to this would be to setup the deployment having two enviroments, each one can be triggered seperately.

[Cristiano Mariano]

Hi guys!

Do you know whether this feature is on Bamboo roadmap?

Thanks,

Cristiano

[Russell Moore]

Meh - is what I had assumed, thanks Jason.

Guess we'll leave it in the old style where we deploy in the build script for now.