This just occurred to me this morning as I sleepily clicked through my usual deployment process, like a good droid. However, I forgot to untick the database deploy part. After the realisation hit me all I could do is stare in horror at the screen, looking for a cancel button and hoping that it will not do something bad to my database that I really didn't want to touch.
I don't think it would be useful to be able to cancel steps that have already started however I would love a cancel facility that would skip all subsequent steps.
I think it would be useful to have a "Stop running deployment" button in the Deployment Server Web Interface so that we can stop a currently running deployment process.
Iain Elder commented
Please implement this to give us a way to recover from a runaway deployment.
If a deployment script enters an infinite loop, we kill the deployment process using administrator tools like Stop-Process and Stop-Service.
It's disruptive for our release engineering team and can interrupt deployments that are otherwise successful.
I described my own experience in the forum:
absolutely a must have functionality :)