_sgbak is killing my build server!

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
jarnold
Posts: 2
Joined: Tue Jul 27, 2004 9:57 am

_sgbak is killing my build server!

Post by jarnold » Tue Jul 27, 2004 10:00 am

I thought I had successfully setup an automated build server using NAnt, and CruiseControl.NET, however after running for 2 days, my project folder (about 800 files) now contains over 100,000 files (and counting). Is there any way to turn off the _sgbak feature?

I am using the vault.exe command line utlity to get the latest version of the code prior to each build.

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Tue Jul 27, 2004 10:18 am

jarnold:

The CLC will honor all client options used within Vault. If you log into the client (using the Vault CLC's user), change that accounts Local Files option to not "Save files in backup folder before overwriting".
Jeff Clausius
SourceGear

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Tue Jul 27, 2004 10:26 am

It sounds like there might be another problem here though if the _sgbak files are being continually created. This would only happen if your files statuses are Unknown. Are you removing your baseline files as part of the process?

jarnold
Posts: 2
Joined: Tue Jul 27, 2004 9:57 am

Post by jarnold » Tue Jul 27, 2004 10:39 am

I am not removing anything, i used the vault client to get the original copy, and it worked great for the first two days. then the NAnt process started timing out. I think I tracked the file creation down to the way Nant processes the detection of vault changes. I turned off the backup file option in the client for my Nant process user account, and it seems to not be creating the files each time. I think for some reason the Vault Client was also 'seeing' the local files as renegade copies, so I am starting with a fresh pull using the account I setup for the automated builds. Hopefully this combo will work.

I'm also toying with the idea of shadow folders to keep it current, but then I am not sure how the change notifications will be communicated to the CruiseControl service to trigger an NAnt build.

Post Reply