Sometimes, developers cancel the onging release deployment. In some cases, the deployment is interrupted in the middle of step execution and changes cannot be reverted easily afterwords. For example, there is one step to restore the database and run some cleaning sql queries. The deployment was cancelled right in the middle when powershell script turned the database in a single user mode and started to restore it. Deployment was cancelled and the database was left in that state. It was required manual intervention to login and revert changes.

My idea is to add possibility to mark the step as atomic and do not cancel the deployment in a dirty way but wait until the step is completed.

It should be added kind of a checkbox to mark the step running in a transaction mode that cannot be cancelled until its completed or timeout.

Cheers.