My deploy on Google Cloud (app engine flexible) takes about 12 minutes to complete, and deploying with zero downtime requires using their API to spin up an alternate then swap it in once healthy.
If any additional commits to our staging or release branches trigger a build in that time they will fail with an error in the deploy phase.
I’d really like a way to stop those build errors because they’re distracting the team and are totally avoidable. Circle already allows earlier builds to be auto-cancelled by subsequent commits to a branch, but since that could interrupt a deployment that doesn’t work here. Instead I need builds to be queued until the deployment is complete and the branch is ready.
Appreciate that this has already been raised twice over the past 3 years, but replies seem to be disabled on those threads so I want to voice my support for it.
Oct '15 - Dev '17
Dec '15 - Mar '17