260
Option to allow failures in Fan-In/Out Workflow
under review
B
Brandon Page
The requires tag in workflows really limits what is possible. Requires makes a lot of sense for the deployment scenario used to demo it, but waiting for a group of jobs to complete (pass or fail) should be an option.
Scenario: Setup -> Run multiple sets of tests in parallel -> Combine test results/coverage results/artifacts and report to PR
That scenario above isn’t possible because if a single test fails in any of the jobs running in parallel the the fan-in step won’t run.
CCI-I-344
Activity
Newest
Oldest
Salil Subbakrishna
Joel Hillacre
Any updates on the implementation of this feature? CircleCI interface did a great job pushing us to use more machines via parallelism but the lack of fan-in on failures is leaving us with less functional than before.
Agustin B
Hi, this feature would be great. I guess we all have the same use case: combine test results no matter if any parallel job failed.
In my case, I would generate a stats report with the most common errors across all test results.
Thibaut
Hi Liya Ai, any update on this? It's been "Under Review" for 1 year now...
Because of this limitation, when we want to aggregate test results, we have to poll regularly from the reporter job. And of course, we spend time machine and money for nothing...
V
Vikram Ambre
Liya Ai Hi, I know that this is in the works, however is there any timeline for this?
Octavious Williams
New
Anton Matveiev
Hi. This is a desired feature for my company. Use case: collect test results from multiple jobs that run in parallel. If some of the jobs fail we want to collect the test results.
T
Test User
Hello,
The idea of such an implementation is already being considered, but, unfortunately, it has not been implemented yet. https://ideas.circleci.com/cloud-feature-requests/p/option-to-allow-failures-in-fan-inout-workflow
T
Test User
Liya Ai, Hello, any updates?
Liya Ai
Test User: Please see response from our PM below: We've been investigating this in conjunction with a related feature to enable filtering of jobs within a workflow. Part of the reason this has been slow is that we try to be very careful with changes to the config syntax. When making the changes we need to maintain backwards compatibility so builds aren't broken without change. At the same time, once we make changes to the syntax they can be hard to back out since some customers start using them and removing those changes might make those configs invalid. We have some ideas we are refining, but given the impacts mentioned above, this might take some time to do the right way. - it was a bit hidden so re-posting here in case you also missed it like I did
T
Test User
Liya Ai: Thank you, we are looking forward to this functionality.
Chris Merck
Yes, PLEASE add this. It would be very helpful for our code coverage job to run after all other jobs have completed, even if there are some failures of the "dependent" jobs.
Load More
→