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

Re: How to lock repository for automated build purposes?

From: Alec Kloss <alec.kloss_at_oracle.com>
Date: Thu, 30 Oct 2008 09:01:17 -0500

On 2008-10-29 20:41, Andy Levy wrote:
> 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.

Assuming your build checks out multiple times from the same
repository, you can also do an svn info on the repository at the
beginning of the build and then do all operations svn operations
with -r <revnumer>. This guarantees your repository is in
viewed in a consistent state all the way through the build and
doesn't require creating a build branch in the repository.

Alec.Kloss_at_oracle.com			Oracle Middleware
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x432B9956

  • application/pgp-signature attachment: stored
Received on 2008-10-30 15:01:43 CET

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.