Re: Pulling one commit at a time.
- From
Avery Pennarun <apenwarr@gmail.com>
- Date
- Aug 24, 2009, 18:19 UTC
- Message-ID
- <32541b130908241119t1b969d30q8c8b484481f30ace@mail.gmail.com>
- In-Reply-To
- <4A92318F.6050105@microchip.com>
On Mon, Aug 24, 2009 at 6:22 AM, Sanjiv Gupta<sanjiv.gupta@microchip.com> wrote:
> Excellent description. Thanks for that. I want to merge commits one by one > because I want to run a regression suite on each commit and therefore know > if any one is causing failures.
Hi Sanjiv,
'git bisect' is an even better way to do this, in my experience. I wrote a program (http://github.com/apenwarr/gitbuilder/) that automatically runs regression tests against all the new versions on all the new branches. It then publishes the results on a web page and via RSS.
gitbuilder does take a shortcut: if commit x passes and commit x+10 passes, it doesn't bother to test commit x+1..9. However, if x+10 fails, it bisects automatically to find the first commit that caused a failure. You could disable this shortcut easily enough, however.
Have fun,
Avery