Cancel a running deployment

[jamesmacwhite]

At present once a deployment has been triggered either manually or by the "on push" trigger, there is no way to cancel it. This can be useful if there is an issue identified before it completes.

Scenario: We noticed our non-live environments having issues with loading build artifacts for recent code deployments, but I had just triggered a deployment to our production environment. I could not stop this process at this point, knowing a bad build was about to cause problems.

[andrewfairlie]

Yeah I've had this need too. I've also similarly thought it would be nice to be able to rollback changes. I know that might be a bit tricky with version changes and project config changes though and may be riskier than just reverting on Git.

[jamesmacwhite]

This comes from an active issue right now with code deployments. They've been a bit wonky today and throwing "internal error". However, it appears artifacts are now missing from the build which is causing issues with missing resources i.e. CSS and assets. Our site is in the 1990's era currently.

Suggest you do not do any deployments for now.

[jamesmacwhite]

The rollback option is sort of related in a few ways, but the ability to just prevent a code deployment from completing if it's not got to the release stage would be generally safe. I can understand the issue of interrupting a release where it has database/project config changes in progress, but by then you'd probably not want to stop it anyway, because you'll have a potentially broken site and a corrupt database, requiring a manual recovery.

[jamesmacwhite]

FYI deployments should be fixed for info.

https://status.craftcms.com/incident/602567?mp=true