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

Updating the working copy for a continuous build process

From: Chris Lambrou <Chris.Lambrou_at_grantadesign.com>
Date: 2006-08-08 18:03:59 CEST

My development team is currently in the process of migrating from CVS to
SVN, and I'm trying to update our continuous build script. Currently,
at the start of the script, our project's trunk folder is deleted, and
an update is then performed in order to retrieve a pristine copy of the
latest repository version. This generally takes a long time, and I
can't help thinking that an incremental update would be quicker. To
achieve this, I assume that I need to carry out the following steps to
the working copy of the trunk folder:

(1) delete any local files not subject to version control (erases any
intermediate and output files generated by the previous build)
(2) svn revert - Revert any modified files to the local repository
version (ensures the subsequent update won't result in any conflicts)
(3) svn update - Obtain any modifications since the last time the build
script ran

Steps (2) and (3) shouldn't be a problem to implement, but can anyone
please suggest how I might implement step (1)?



P.S. Will step (2) discard my local changes completely, or will
Subversion rename any locally modified files before reverting? If so, I
may have to swap steps (1) and (2).

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 8 18:02:12 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.