Rolling Deploys and Auto-Deploy 30 second delay

[pixman20 (Andrew)]

Due to the lack of rolling deploys with the DeployRelease feature, we’ve had to create an environment per deployment target to ensure all of our projects deploy fully to 1 machine before moving to the next.
We have an application level project (i.e. MyApplication) that coordinates and deploys many other projects (i.e. MySubApp1, MySubApp2, etc).

Unfortunately, this is making deploy times unnecessarily long since we have to wait up to 30 seconds for the next Auto Deploy trigger to cause the next environment/server deploy to kick off.
(Some further background is available here:

Lifecycle automatic deploy not firing

We are currently using 2018.8.12 and are having an issue where a release is not automatically firing the deploy for the subsequent environment. Our best guess of the cause is that we had a failed deploy (due to connectiviy issues), which after restarting it and successfully deploying appears to have caused issues with the automatic deploys. Our setup is as follows: We are deploying Project A, which deploys project 1, 2 and 3 to several different environments subsequently.- We have several en…

and here
Allow Deploy Release step to be used in rolling deployment · Issue #4418 · OctopusDeploy/Issues · GitHub)

We’re currently in a rough spot because we cannot roll deploys using DeployRelease, and we cannot continue migrating more projects (which use more servers) to Octopus without dramatically impacting deployment times due to the 30 second Auto-Deploy schedule. For example, with 10 servers it can add up to 4.5 minutes just waiting for the Auto-Deploy to kick off, and 100 servers could add up to almost 50 minutes of wasted time .

I’m hoping that one of the following is possible to allow us to continuing growing in our use of Octopus:

1. The DeployRelease rolling deployment feature gets completed
2. The Auto-Deploy schedule is handled via event triggers or the schedule delay can be configured
3. Perhaps there’s another workaround for the meantime. I’ve considered looking into using the API to see how to re-invent the Auto-Deploy mechanism that immediately triggers the next deploy upon completion of another, but I’d like that to be a completely last resort.

Please let me know if there’s any progress being made on #1, if #2 is a possibility, or any suggestions for how to workaround both of them using #3 above.

Thank you!
Andrew