As a matter of fact, manually checking out all the intermediate commits and building/testing those is precisely what our team does. Except, it's not done manua

As a matter of fact, manually checking out all the intermediate commits and building/testing those is precisely what our team does. Except, it's not done manually, we have a set of tools that walks along a branch and tries to build each revision, storing the build/test status using the commit's SHA-1 hash as a key so that we don't waste effort rebuilding things unnecessarily. Then, this is used for our code reviews to verify that each commit on the branch to be integrated has a clean build/test status saved -- or an explanation why not. We've given some thought into writing a version of git bisect that takes this cached data as input to select better trees to try given some set of known broken commits, but that hasn't happened quite yet.