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

Re: Performance Question

From: Tom Mornini <tmornini_at_infomania.com>
Date: 2005-01-11 07:32:34 CET

Hash: SHA1

On Jan 10, 2005, at 5:35 PM, Peter Valdemar Mørch wrote:

> G'day Peter,
> Monks, Peter wrote:
>> Why not use "svn export" instead of "svn checkout"? You won't end up
>> with a working copy, but unless your build scripts modify the code and
>> then commit the changes, that shouldn't be an issue.
> I almost always conclude a successful build with:
> $ svn cp -m "Created tag for build X.Y" . $repos/tags/PROJ_X_Y
> So I need it to be a working copy.

That's sort of backward, isn't it?

Why not tag first, then build on the tag? That *completely*
eliminates the possibility of the tag and branch being out
of synchronization.

I'm sure the chance of the automated build working copy
being changed between the make and the tag, but why take a

Uncertainty in automated build processes is undesirable.


svn cp URL_TO_PROJ/trunk URL_TO_PROJ/tags/PROJ_X_Y
svn export URL_TO_PROJ/tags/PROJ_X_Y

P.S. It's often a good build from source controlled and
      exported tool sets as well, and checking back in
      compilation targets to the same tag is also a big
      win in most situations.

- --
- -- Tom Mornini

Version: GnuPG v1.2.4 (Darwin)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 11 07:35:59 2005

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.