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

Re: running 2 update commands on one working copy at the same time

From: Stephen Butler <sbutler_at_elego.de>
Date: Tue, 27 Sep 2011 10:58:26 +0200

On Sep 27, 2011, at 9:20 , Jan
 wrote:

> Hello,
>
> I've got 2 batch processes, one compile CHUI files and another compiling
> WIN32 files. They use the same working copy and update the working copy
> before starting.
> I wonder if this is safe: if the 2 update commands run at the same time,
> will this cause issues? So far it appears to work just fine, but I'd
> rather be sure than sorry.
>
>
> ps.: Both compilers run on the same machine and just invoke svn.exe
> --non-interactive --accept theirs-full --depth infinity update
> c:\workingcopyname, so there won't be a problem with incompatible clients,
> the client is the same. I just wonder if I could have problems with a
> locked working copy or something like that. The working copy is only used
> for compiling, there are never any changes in the working copy. SVN Server
> & Client: 1.6.17, OS WIN32, server = Apache.

Subversion operations that modify the working copy, such as update, use
a Subversion-internal "administrative" locking to ensure that the operations
don't collide.

It's possible that build process B runs an update while build proces A is
already compiling. Then the effective source code of build A might
include files from different revisions, which is difficult to reproduce.

Regards,
Steve

--
Stephen Butler | Senior Consultant
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
tel: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elegosoft.com
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
Received on 2011-09-27 10:56:47 CEST

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.