How do you deal tests overflow these days? Is that even a problem for you? How big the project is? Maybe most tests are cheap and fast?
Commit
a94b1bc
Doubled our amount of Gitlab runners and optimized the pipelines a lot. Still looking for ways to improve because the amount of test is growing fast.
commit a94b1bc
We did that as well. Moved to Blacksmith, optimized many tests, added speed traps, implemented TIA, split logic from IO (so more unit tests), and booting only the parts of framework the tests needs. Manageable so far, but I wonder what else people do 🤔
Im curious to hear more about your pipelines, the runner pool, and how your using them. I've been working on https://chickadee.run which are drop-in replacement for github runners (like blacksmith) and just trying to hear more about how others are using runners in general
chickadee.runEphemeral GitHub Actions runners · chickadee.runFresh Linux VMs for GitHub Actions. A small, open, self-hostable runner platform from Plover Digital.
Just doubled the about of concurrent github runners for my org but it's still a huge bottleneck. might just need to continue looking into optimizing and seeing what i can offload to local hardware. something like blacksmith isnt really an option for me atm either