Home/ Questions/Q 40475
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T15:01:46+00:00

We use a CruiseControl.Net/NAnt/Subversion stack for CI. Doing a fresh checkout for every build

  • 0

We use a CruiseControl.Net/NAnt/Subversion stack for CI. Doing a fresh checkout for every build is way too time-consuming, so currently we just do an update on a working copy. However, this leaves the possibility that orphaned files may remain in the working copy, after being deleted in source control. We have tried using the NAnt delete task just to remove all code source files before an update, but this can corrupt the working copy. Does anyone know a fast way to run a build on a clean and up-to-date working copy? EDIT: We are on SVN 1.3.2

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. If you do just ‘update’, SVN will delete all the files that were deleted in the source control. However files that were created during build process might still be there and might interfere with new build. I’m not sure if SVN has a command to delete them but I guess you could do that with a little script, SVN definitely could tell you which files are under source control and which aren’t.

    • 0