Add ability to use run conditions for child steps
The only way to specify a rolling deployment is by grouping several steps into one parent step.
Child steps cannot specify any run condition (success, fail, variable) but some child steps run condition can be based on several factors controlled by run conditions.
I already opened a discussion here: http://help.octopusdeploy.com/discussions/problems/55380-add-ability-to-use-run-conditions-for-child-steps
Run conditions were made available for child steps in Octopus 2020.2: https://octopus.com/blog/octopus-release-2020-2#better-run-conditions
This is the latest roadblock as to why we still have not been able to take advantage of "Deploy A Release" functionality.
Alexander Rauan commented
This ability would be great with the new Runbook feature, which in some cases will have conditional requirements within a Task.
For instance we are testing out creating a Runbook to ensure that the frameworks on our servers are up to date. The task runs on each server in our infrastructure. As the final step per server per run we want to check if a restart is required based on a previous step, and trigger it.
I have a similar situation & will be interested to see this change.
Mike Skutta commented
I have a similar situation as Chris mentions. We have a rolling deployment. If there is a failure, we would like to rollback changes. We need run conditions for child steps to support this.
Run condition for child step based on variable would be good
Chris Trotter commented
We are working on a canary/blue-green deploy process. Using the 'rolling deploy' for our web app, it makes a pile of changes that require rollback on failure. On the assumption that exiting the rolling deploy section means you lose the specific instance you were communicating with (i.e. going from working on instance 2 of 3 back to 1 of 3), it makes for a lot more work to figure out which instance is broken and needs reverting.