Chris Lambrou wrote:
>Hi,
>
>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)
>
>
All our build output goes into a single "build" directory, so we can
remove this before the build starts. None of the build ouput is under
version control.
>(2) svn revert - Revert any modified files to the local repository
>version (ensures the subsequent update won't result in any conflicts)
>
>
There are never any local modifications in our continuous build working
copy (all we do is build there), so svn revert is unnecessary.
>(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)?
>
>
>
So things are very simple the way we work here:
1) Remove build directory
2) svn update
3) build
Of course, you may have other requirements which mean this wouldn't work
for you ...
Regards,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 8 19:25:49 2006