Thanks for getting in touch! I believe that the way some of our customers have combated this particular issue is to create a standalone project, that is a PowerShell script, that determines what servers are on or offline and marks them as disabled and activates those that were disabled and offline. It isn’t very elegant, but Octopus does take a list of machines at the start of a deployment, and cannot modify that list while the deployment is active, so a separate project was the only solution.
We are working on an option to allow deployments to happen when a machine in the list is offline by allowing you to continue to deploy to online machines, but that is still a little while away, and doesn’t help you now.
Vanessa
Yep! It was part of 2.6. If you check this blog post it describes the feature a bit: https://octopusdeploy.com/blog/2.6 (Under “Skip Offline Machines”)