Re: How to lock repository for automated build purposes?

On Tue, Oct 28, 2008 at 21:50, E.K. Lee <ek_lee_at_hotmail.com> wrote:
> I need a way to prevent developers from committing files while an automated
> build process is started. Is there a way to achieve this with the default
> svn command line tools (the svn lock seems to work only on files)? Or is
> there an easier way to lock a repository temporarily? Thanks.

Rather than put your developers into a situation where they risk
losing work or diverging too drastically without committing, run your
automated build from a tag which only a "build manager" can commit to.

Also, because repository operations in Subversion are atomic, when
your build process executes its checkout/update it should not get any
"pollution" if someone commits to the same path between the time the
checkout starts and completes.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-30 01:41:57 CET