Feature: Using git bisect skip to ignore compilation errors

Depending on you commit policy, ``git bisect`` may have a hard time to identify which commit actually is the faulty one. Take this history:

1. Known good commit, passing tests
2. Good commit
2. Good commit but with compilation errors
3. Good commit but with compilation errors
4. Good commit fixing compilation of 3 and 4
5. bad commit causing a test failure git bisect should find
6. known bad commit, failing tests

In scenarios where you e.g. start a big refactoring job, you might actually have commits in-between where the build fails. But if you want to identify when a test started failed, you want to skip these. Otherwise, in the above git history, the Jenkins git blame plugin would return the third commit as the test jobs fails there.

So an option to ignore compilation failures but not test failures in the Jenkins git bisect plugin would be really helpful