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

Re: fast revert+update for a continuous integration process?

From: Duncan Murdoch <murdoch_at_stats.uwo.ca>
Date: 2006-04-20 19:47:45 CEST

On 4/20/2006 1:31 PM, Dave LeBlanc wrote:
> Hello all, just a quick question:
>
> We have a cruise control machine, and often want to grab the latest copy of
> code. Naturally, we'd prefer to not pull down the entire tree when we have
> the prior version sitting there already.
>
> We can't use 'svn update' on our build machine, because it leaves
> non-versioned files (build artifacts), and chokes on case changes in
> windows. In essence it doesn't reliably leave us in a clean and pure state
> for the next test run.
>
> Something like a "revert to head" command, that also deletes non-versioned
> files would be perfect - this would speed up a lot of people's cruise
> control builds for sure.

In general, I'd say it's worth solving the problem of not being able to
"make veryclean" and return to a pristine state, but in the meantime,
how about this:

Maintain one checked out copy where you never do any builds, so it stays
clean. Use svn up on that copy.

Use rsync or some other utility to restore your build copy to be
identical to that.

Duncan Murdoch

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 20 19:49:52 2006

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.