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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs