When we have a very complicated deployment like this, we simplify our
deployment pipeline by building up a parallel network with all the
correct versions installed. The actual deployment is pointing the load
balancers to the new parallel network. Rollbacks are simple. When the
deployment is done, we just throw away all the old hosts from the old
On Wed, Aug 22, 2012 at 9:24 AM, Diptanu Choudhury <dipta...@gmail.com> wrote:
> A couple of questions, do you have a Deployment Pipeline already? If not
> then you will have to think about constructing one so that the artifacts can
> be deployed automatically to different environments. If you do, then first
> of all you will have to look at your current deployment pipeline, does it
> always aid in moving forward by checkout out code from the source control
> and progressing the built artifacts all the way through to your different
> environments? Or does your deployment pipeline allow you to deploy any
> arbitrary version of your application?
> Rollbacks are trickier because they involve restoring the state of the
> We have been doing all this quite successfully for a long time now.
> On Wed, Aug 22, 2012 at 4:30 PM, jdtangney <jo...@jdtangney.com> wrote:
>> We are extending our Continuous Delivery process and I am looking for
>> Each release consists of several components, each of which is installed by
>> Do you have any thoughts about how we should approach this? Are there
>> Apologies for the vague and open-ended question.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.