TL;DR Lazy compute intensive way to find what non-commit change broke your tests... if your tests are any good.
Is CI and presubmit testing lazy?
Automating Git Bisect with Ephemeral Environments
21–22 of 22 posts
Re: Automating Git Bisect with Ephemeral Environments
#22Interesting idea! The real bottleneck here is likely not the number of test runs, but rather the overhead of environment setup and tear down. This is where ephemeral environments really shine if they can be optimized for quick startup.