Rails framework upgrades with git-bisect(brad.posterous.com)
brad.posterous.com
Rails framework upgrades with git-bisect
http://brad.posterous.com/rails-framework-upgrades-with-git-bisect
5 comments
If anyone needs to bisect an intermittent bug, I have written a bayesian version of git bisect. It can be found at: http://github.com/Ealdwulf/bbchop/tree/master
I can personally vouch for the awesomeness of 'git bisect', especially when combined with 'git rebase' to reconstruct trees minus troublesome commits.
Like many tools, I think git bisect's advantage comes from reducing the amount of thinking that you need to do to accomplish a task. Before git bisect I'd often stare at pieces of broken code or poke around in a debugger for hours on end. Now, ~1 hr or so with git bisect and friends, and the job is done...and I get to spend brain cycles thinking about something else.
Like many tools, I think git bisect's advantage comes from reducing the amount of thinking that you need to do to accomplish a task. Before git bisect I'd often stare at pieces of broken code or poke around in a debugger for hours on end. Now, ~1 hr or so with git bisect and friends, and the job is done...and I get to spend brain cycles thinking about something else.
The coolest part of git bisect is the run option: http://tlrobinson.net/blog/2008/10/01/git-bisect-run/
If you can write a shell script that returns 0 when the test passes and 1 when it doesn't, git bisect run will do the tedious part for you.
If you can write a shell script that returns 0 when the test passes and 1 when it doesn't, git bisect run will do the tedious part for you.
My brain just gitsploded. More like this, please.
my_script should return 1 if tests failed, or 0 if they passed. Git will then go off and find the commit that broke things.