Adding more information about the behaviour of manual interventions #2580
Conversation
This file contains 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
steve-fenton-octopus
approved these changes
Dec 2, 2024
…m/OctopusDeploy/docs into manual-intervention-clarification
steve-fenton-octopus
approved these changes
Dec 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Background
It was observed that our docs do not make it clear what should happen when a manual intervention is aborted.
What Octopus Deploy does, is that it treats that like any other failure, and then proceeds to evaluate the run conditions of subsequent steps. So if a step is setup to run on a previous step failing, then it will run.
This PR aims to help specify this behaviour so it is more clear to our customers on how manual interventions should behave.
Example
We added a sample to the docs on the Octostache variable that you could use to control steps with variable conditions.
This sample was tested, and here are the results:
The configured variable:
A deployment where we aborted the manual intervention:
A deployment where we proceeded with the manual intervention:
