Sometimes you might find yourself having created a deployment that you don't need anymore, or that is causing other deployments to get queued behind it.
Previously, it was necessary to wait for such deployments to complete, and then delete them. As of today, however, you can immediately cancel deployments if they are no longer required.
In order to prevent a deployment from continuing to build, you can now click on the newly added "Cancel" button that shows up on the dashboard while your deployment is building:
Canceling an ongoing deployment from the dashboard.
Once you've canceled the deployment, any deployments queued behind it will start building.
If you're creating new deployments very quickly, the most recently created ones may get queued until the oldest ones have completed building.
Canceling some of them will allow the others to start building. A better way to get them to start building, however, is to increase the amount of Concurrent Builds on your team's "Billing" settings page:
Increasing the amount of Concurrent Builds.
Please note that the Concurrent Builds feature is only available to teams.
Preventing ongoing deployments from building is now simply a matter of clicking a button.
For teams that would like to increase the amount of deployments they can build at the same time, however, we recommend increasing the amount of Concurrent Builds.
Let us know what you think about this change.