Ability to do swing site deployment between staging and production role
We can deploy a release to staging and then promote it to production, it would be great if as part of the promote, we could swing the existing production deployment to staging and then promote the new release to production and also give an option to rollback to previous release.
This is a really interesting suggestion and topic. What I’m not sure about is exactly what Octopus would need to do.
Normally for these kinds of things, you deploy the site, then change the load balancer to send requests to the new servers (the swing).
What exactly does Octopus need to do? Should we automatically migrate the machines in the environment that we deployed to between the staging and production environments, and move the deployment to production too (or, should we just rename the staging and production environments?)
Eric Hexter commented
I would think of the swing as , repointing IIS websites from one release to the other, then for services, starting and stopping the respective services. Right now this can all be done with powershell, but it would need to be executed in parallel in order to swing everything at the same time. I think its better to do this with a load balancer rather then swap the iis settings since, it will still force the app to pay the startup costs.
Andrew Armstrong commented
I think this is also known as blue/green deployments