BT

Continuous Check-Ins with Mercurial

| by Jonathan Allen Follow 636 Followers on Feb 16, 2011. Estimated reading time: less than one minute |

One of the major benefits of a distributed version control systems is that each user gets their own versioned workspace. Leon Bambrick is experimenting with continuous check-ins, where in each successful build also triggers a check-in. He writes,

This is clever because it means that every tiny change you make is tracked. And it's stupid for the same reason. The main reason it's stupid is that it means every time something has changed you are asked to enter a commit note in a notepad.

It's quite annoying at first. But soon you get into the spirit of it. You realize that it is making you act in a more mindful manner. You are concentrating on every build, more aware of what you are doing, and better focused on your tasks.

For more on how he setup Mercurial within Visual Studio and his thoughts on the experiment see his post titled Mercurial workflow for personal projects.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

clever idea by Chris Sutton

The idea is clever as Leon noted, but that is far too tight of a check-in cycle. The commit messages will be too fine grained. Or maybe I would adapt to building less often.

I do many intermediate builds that wouldn't make for logical check-ins. I think it would be more interesting to trigger the check-in when your test suite passes.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

1 Discuss
BT