When deploying to many machines, Octopus can perform a rolling deployment, deploying to one machine, then another, and another, waiting each time for the deployment to succeed. You can even modify the window size - deploying to 3 machines in parallel for example.
Have Octopus automatically deploy the application to new machines that are provisioned as part of a cloud auto-scale.
For load balanced applications, deploy to a subset of inactive servers, then swap them for the active servers.
If you're deploying to the cloud, you can provision the environment as part of the deployment, giving you fully immutable infrastructure and ensuring your deployments are repeatable.
Recurring Scheduled Deployments
Ensure the latest version of your project is in the hands of QA testers every morning. Set the deployment time, timezone and even factor in daylight saving considerations.
You might also like...
Currently updating a deployment process in @OctopusDeploy. I forgot how easy this was to use, everything just makes sense.— David Swindells (@d_swindells) January 30, 2019
Tools like @OctopusDeploy can be great in enabling culture change, we've been able to scale and improve our configuration story since we started using it.— Neil Chalk (@_neilch) July 19, 2018