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. Schedule deployments to recur daily, on certain days/months or as a cron expression at single, minute or hourly intervals. Set the deployment time, timezone and even factor in daylight saving considerations.
You might also like...
@OctopusDeploy Really liking the new GUI in @OctopusDeploy 4.0, both good looking and fast. Great work!— Johan Boström (@zarx) November, 21 2017
I’d stand by @OctopusDeploy every day of the week. Honestly couldn’t imagine our CD working as smoothly without it.— Ben Macpherson (@BenjiMac93) November 18, 2017