Auto-cancel builds for default branch
under review
E
Emil Ong
Originally asked here: https://discuss.circleci.com/t/auto-cancel-builds-on-default-branch/5536
We would like auto-cancel to apply to the default branch, specifically because we have a deploy action associated with it. The deploy is slow and multiple builds are often racing with each other and we occasionally get an older build that finishes after a newer one, leaving us with older code deployed. (This is only for a staging environment deploy in our case though.)
CCI-I-214
Sevket Kursad KAHYA
We definitely need these. Because of the slow deployment process we have in master, it may end up with older version to deploy to prod due to race conditions.
Cassandra Stone
Any updates here?
George Kronberg
4 years? More like 6. The initial discussion thread happened in Aug 2016. It's not just a nice-to-have -- it's truly a critical feature, that is somehow still not in the product. If you merge 2 PRs one right after another, the earlier merge can take a few seconds longer to build and ultimately override a later merged build that is already in production.
Liya Ai
under review
Hi Everyone - just a quick update here, we know this is a highly requested feature request and our teams are actively evaluating how to improve this experience. Will post more updates as they come in, thanks!
Peter Sankauskas
4 years and we still have to do this silly work around because you insist on forcing your antiquated conventions on your customers.
Dave Sueltenfuss
This is a must have for my project!
Esa Nuurtamo
This is a must have feature!
I think this is a business choice that CircleCi made to make more money… It is ridiculous that I have to pay for these redundant builds for default branch that do not add any value to our testing process!
Liya Ai
Y
Yann
You could also implement this workaround > https://discuss.circleci.com/t/auto-cancel-redundant-builds-on-the-default-branch/39468
arnorhs
what's up with this feature? I'd really like to be able to auto-cancel the default branch build, but this issue/feature seems to have gone pretty quiet, is there a new/different approach to this these days?
Load More
→