Open joscha opened 6 years ago
We'll discuss, interested to know a bit more about what you'd use this for!
We have a step that is changing infrastructure - it has a rollback/cleanup mechanism at the end if something went wrong. This rollback is never executed if the job gets cancelled, so we do this:
I named the image poor man's do not cancel
, we would like to...improve this for obvious reasons.
One place this would be useful is in tandem with "cancel intermediate builds". We'd like to cancel pending deploys, but not interrupt running deploys.
This would be a huge help for us too regarding the cancel intermediate builds! The issue is when someone deploys a branch, they would need to remember not to push to their branch until the deploy is complete, otherwise it would be cancelled. Some deploys take a long time, so we cant use this feature.
+1 - for the same reasons as above!
We'd also benefit from the concept of an non-cancelable step. Basically the same reason. If a developer cancels a build when a specific step is running, we get state-locks in pulumi.
But it would be nice to be able to cancel a build; and wait for the non-cancelable steps to finish
Any chance to get an option
cancelable: true|false
, disabling the "Cancel" button in the web UI?