If I cancel the release pipeline which is using release orchestrator is there a way I could use release orchestrator to propagate the cancellation to any releases it triggered? I don't want to leave around lots of zombie child releases consuming resources or waiting for manual approvals which no longer matter because the orchestration job was cancelled/abandoned.
I presumably would need a separate invocation of the task with a custom condition to run always (ie even if previous tasks failed) which knows the release IDs of the triggered releases to send cancel events to?
It's a good idea. I think the orchestrator should be even cancelling the target release by default. I will do my best to add this feature in the coming release.
If I cancel the release pipeline which is using release orchestrator is there a way I could use release orchestrator to propagate the cancellation to any releases it triggered? I don't want to leave around lots of zombie child releases consuming resources or waiting for manual approvals which no longer matter because the orchestration job was cancelled/abandoned.
I presumably would need a separate invocation of the task with a custom condition to run always (ie even if previous tasks failed) which knows the release IDs of the triggered releases to send cancel events to?