Separate the Build Strategy from the repository configuration.

I've used Cruise Control with subversion for several years. We like to have code exported rather than checked out, so each build is from scratch. Cruise provided the modificationset which allowed for checking a repository for changes but not checking out the code. It does this by executing svn log between the build time and the last successful build. What I'm asking for is something similar. Where the build strategy can be to poll the repo (or multiple repos - BAM-866) but not checkout the code. So, the repository could be set to none.

Another alternative would be to allow an svn export from the Source Repository when svn is chosen.