Docs: Reflect resilient deployments on Octopus Cloud#3218
Open
lucyjspence wants to merge 1 commit into
Open
Conversation
lucyjspence
changed the title
lucyjspence
force-pushed
the
docs/resilient-deployments-cloud
branch
from
84dccbd to
042187c
Compare
Deployments and runbook runs on Octopus Cloud now survive node restarts and maintenance windows: they pause and resume automatically rather than failing. Update the customer-facing docs that still framed task failure during outages as expected behaviour. - maintenance-window: replace the "resilience is future roadmap work" hint with shipped behaviour; scope the shutdown-timeout note to deployments/runbook runs (other system tasks may still be abandoned) - Cloud FAQ: add "What happens to my deployments during a maintenance window?" - bulk-operations rerun script: add a Cloud-obsolescence note (still relevant for self-hosted HA) Scope is Octopus Cloud only. Self-hosted HA pages are intentionally left unchanged — resilience is not yet on self-hosted. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lucyjspence
force-pushed
the
docs/resilient-deployments-cloud
branch
from
042187c to
9369798
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Deployments and runbook runs on Octopus Cloud now survive node restarts and maintenance windows — they pause and resume automatically rather than failing. Several docs still framed task failure during outages as expected behaviour, or described resilience as future roadmap work. This updates them.
Scope
Octopus Cloud only, deployments and runbook runs only. The claim is resilience shipped on Cloud, not maintenance windows removed — maintenance windows still exist; deployments and runbook runs now survive them.
Other task types (e.g. system tasks, health checks) are not resilient yet, so the maintenance-window page keeps the "other in-progress system tasks may still be abandoned" caveat.
Self-hosted HA pages are intentionally left unchanged — resilience is not yet on self-hosted.
Changes
octopus-cloud/maintenance-window.mdoctopus-cloud/frequently-asked-questions.mdoctopus-rest-api/.../rerun-deployments-and-runbooks-after-node-shutdown.mdx🤖 Generated with Claude Code