...or how I found out who broke JIRA's coverage build last night. JIRA's Clover Code Coverage build is scheduled to run once a day. Yesterday someone checked in something that broke 194 tests. The problem is there were 18 commits by 7 unique authors and none of the commits come with a helpful message like "Warning, this commit is the one that will break the coverage build!" To try to narrow down which of the commits was the problem, I decided to use an automated bisection of commits. git comes with

Continue reading »