DVCS comparison for our organisation: decided

Nicholas Allen allen at ableton.com
Tue Oct 16 12:39:19 BST 2007


Ben Finney wrote:
> Nicholas Allen <allen at ableton.com> writes:
>
>   
>> But I think these hooks are of limited benefit for running test suits
>> and build commands. I guess it depends on the size of your project but
>> I like to commit often and expect a commit to be on the order of one
>> second.
>>     
>
> Yes, which is why I said the hook needs to be per-repository or
> per-branch. The developer commits to their own branch without the
> hook, but try to commit to the anointed canonical branch and the test
> suite runs automatically to determine whether the commit succeeds.
>
>
>   
I guess that is another way of doing it. It probably means that if 
multiple developers commit to the trunk at similar times you will get 
locking issues (even on Mercurial). When one person is committing to the 
trunk and the test suit is being run then he will have to wait until the 
first developer's commit finishes. This may take a long time and the VCS 
will probably time out after a while. It means that developers will have 
to keep trying and the order of commits will be lost. This may not be a 
problem for a small team with only a few developers but it does not 
scale well on large projects with many developers (so this approach 
would be unusable for us). But if it works for you then it is a simpler 
solution.

Nick



More information about the bazaar mailing list