Hi What actions CC.Net takes will depend entirely on the Task blocks you set up. If you only want to check out from source control, you'll need to use the <nullTask/> together with some <sourcecontrol type="svn"> blocks.
If you want to copy the files, to avoid pulling across .svn/ folders, or maybe to another server you could use the <execTask> with a command script. If you want to do an svn export directly, NAnt has a good svn task that might fit your purpose. Someone I work with recently wrote a codeproject article about using CC.Net for things besides builds. It might give you some ideas: http://www.codeproject.com/KB/dotnet/cruisecontrol_continuous.aspx Dave Documentation on <nullTask/>: http://confluence.public.thoughtworks.org/display/CCNET/Null+Task Documentation on <sourcecontrol>: http://confluence.public.thoughtworks.org/display/CCNET/Source+Control+Blocks NAntContrib's <svn-checkout/> task: http://nantcontrib.sourceforge.net/release/0.85-rc2/help/tasks/svn-checkout.html On Sat, Sep 27, 2008 at 1:07 AM, briankb <[EMAIL PROTECTED]> wrote: > > I have a single repository called "projects" which holds our website > projects. I'm using VisualSVN Server and everything is running on a > Win2008 server box. > > Repository Example: > http://dev:8081/projects/clientA/alphadotcom_current > /documents > /alphadotcom_next > /clientB/betadotcom > /clientB/documents > > Files for IIS7: > C:\Websites\websites\alphadotcom_current > C:\Websites\websites\alphadotcom_next > C:\Websites\websites\betadotcom > > File Server: > Z:\Backup\clients\ClientA\documents > > so http://dev:8081/projects/clientA/alphadotcom_current should update > C:\Websites\websites\alphadotcom_current > > and http://dev:8081/projects/clientA/documents should update Z:\Backup > \clients\ClientA\documents > > I tried adding a post-commit hook but there are issues. First being I > can't get it to work using VisualSVN Server. Second issue is I only > want to push files to the IIS directory from specific repository > paths. > > Is it possible to setup CCNet to handle this file management and not > trigger a build? I don't need to actually build the dll's for our > primary clients website as its a mix of ASP and .NET and is compiled > on the server as pages are rendered. > > > >
