G'day Peter,
I do the same thing, except that I perform a server-side copy instead
of copying from a working copy.
eg.
svn cp -m "Created tag for build X.Y" $repos/trunk $repos/tags/PROJ_X_Y
Note that there are a few more details to it than this, in order to
insulate the process from any untimely commits that occur between the
build and the tag. I'm not convinced I've worked out the most elegant
solution for that problem yet, but what I have gets the job done and
I'd be happy to explain it if anyone is interested (not that it's
particularly complex).
Cheers,
Peter
----------------------------------------------------------------------
Peter Monks http://www.sydneyclimbing.com/
pmonks_at_sydneyclimbing.com http://www.geocities.com/yosemite/4455/
----------------------------------------------------------------------
> -----Original Message-----
> From: Peter Valdemar Mørch [mailto:nospam@morch.com]
> Sent: Monday, January 10, 2005 5:36pm
> To: Monks, Peter; Subversion Users
> Subject: Re: Performance Question
>
> 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.
>
> Peter
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 11 02:56:52 2005