2009-01-23

An automatic way to figure out which commit broke the build

Atlassian Developer Blog - git bisect...:
"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 a built-in utility called bisect. This isn't unique to git. You can even do it with subversion via svn-bisect. The idea is that you tell it a good revision and a bad revision and then git helps you perform a binary search to narrow down exactly which commit broke things."

Change has come

Front pages all over the world after Barack Obama's Inauguration Day in january 2009, viewed as a zoomable portait of Obama.

read more | digg story