[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Re: Update before commit

From: Dave Grundgeiger <dave.grundgeiger_at_codenouveau.com>
Date: 2007-02-14 22:35:36 CET

> Could two developers who have just done an update to their working copy
> and
> are doing two different parts of the code (with a dependency to each other
> though) do a build/test cycle locally and determine their changes are
> good.
>
> Developer 1 commits his changes, then developer 2. Because developer 2
> didn't modify the same files that developer 1 did, this second commit goes
> through successfully. But because those files are dependent on each other,
> the repository doesn't build?
>
> Of course the odds of this happening aren't great, but is what I've
> described a possible scenario (or am I missing something)? How would you
> get
> around this or handle this when it happens?

This is why I love continuous integration. In this situation the automatic
build will fail, send an email to the team, and developer 2 will fix it or
talk to developer 1 as necessary.

Dave

Dave Grundgeiger
CodeNouveau, LLC
Develop .NET Software with Open-Source Tools
http://www.codenouveau.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 14 22:36:23 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.