Support automatic retry of failed builds
A
Aaron
It would be great if CircleCI allowed you to configure an automatic retry of a build upon failure. Ideally, you would be able to specify the max number of times you would like it to retry.
CCI-I-935
S
Steve Mena
Ironically, we need this to retry transient failures in orb publishing due to a "Something unexpected happened" error.
G
Gonzalo Serrano
Sebastian Lerner it does not solve the issue, which is automatically re-run the failed tests.
S
Sebastian Lerner
Hi folks, we do not have to configure automatically retries, but we do have something that should help some of the scenarios where an automatic retry would be wanted.
Currently in a closed preview/beta: https://circleci.com/docs/rerun-failed-tests-only/
Let me know if there are questions, you can comment on our community forum as well: https://discuss.circleci.com/t/product-launch-re-run-failed-tests-only-circleci-tests-run/47775/4
E
Ernest Katta
we need this feature. especially for QA framework executions
E
Evgeniy Sabilin
We need this
B
Brian Carp
I came here looking for this. Such a thing would be very helpful to resolve an issue with certain steps that interact with external services or steps that have to wait for resources to load that are irreparably flaky. Please consider adding a
max_retries
parameter or something similar!Eddie Shafaq
With GH merge queue this would be great feature to prevent the merge train from being stuck
Ash O'Farrell
This would definitely come in handy for situations where the failure is very likely to be transient. For instance, we run a link checker, and that will fail during brief outages of the websites we are linking to.
J
Jonathan Arnett
We have some custom bash logic to retry our test suite when it fails. However, retrying the test suite is _slow_, as you would imagine. I would love greater visibility into transient failures without failing people's builds, so that they can be investigated.
A
AJ Schmidt
Would also like to see this implemented. Any updates here?
Load More
→