~sak files

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

Moderator: SourceGear

Post Reply
matt_stephens
Posts: 27
Joined: Wed Mar 08, 2006 4:22 am

~sak files

Post by matt_stephens » Tue Apr 04, 2006 10:55 am

We've just got our server installed and are moving our code over to Vault. We were just browsing the list of recent checkins and we have loads of files like ~sakb293618101c657e2.tmp with a comment about the file being checked in by Visual Studio to test the vault capabilities.

There seem to be an awful lot of these files already, can you tell us what the rules are for when these files get created and why they do?

Also, if you try to view the file in the vault website it gives an error page back. Maybe thats because the file has been deleted from the repository but an ASP.NET error page seems a bit harsh!?

Thanks

Matt Stephens

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

Post by dan » Tue Apr 04, 2006 3:20 pm

These files are created by Visual Studio anytime someone binds/unbinds a project to source control. The can safely be deleted and obliterated, as VS never uses them again.

nroberts
Posts: 12
Joined: Thu Jul 27, 2006 10:36 am

Post by nroberts » Thu Aug 03, 2006 4:36 pm

How can I keep them from triggering a build based on modifications in CC.NET?

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

Post by jclausius » Fri Aug 04, 2006 8:15 am

Take a look at exclusion filters within CC.Net
Jeff Clausius
SourceGear

matt_stephens
Posts: 27
Joined: Wed Mar 08, 2006 4:22 am

Post by matt_stephens » Tue Aug 28, 2007 4:56 am

Can you provide any more info about exclusion filters with vault?
I am just evaluating ccnet and am having real trouble getting it to build properly with the buildCondition IfModificationExists.

We are using vault 3.5.0 (4741) and ccnet seems to think there are no changes even though there are. A forced build works ok and i have made sure the servers time and client time are pretty well syncronised.

Can anyone provide any tips or reference to getting ccnet working with vault?

My test ccnet.config is as follows:

Code: Select all

<cruisecontrol>
	<project>
		<name>MKSVault</name> 
		<state type="state" directory="C:\CCNet" />
		<workingDirectory>c:\ccnet\</workingDirectory>
		<artifactDirectory>c:\ccnet\artifact\</artifactDirectory>
		<sourcecontrol type="filtered">
			<sourceControlProvider	type="vault"
					username="xxx"
					password="xxx"
					host="xxx"
					ssl="true"
					repository="Default Repository"
					useWorkingDirectory="true"
					workingDirectory="c:\source\"
					autoGetSource="true"
					folder="$/Matt/"
					applyLabel="true"
			/>
	    		<exclusionFilters>
		    		<pathFilter>
    					<pattern>**/~sak*.tmp</pattern>
    				</pathFilter>
			</exclusionFilters>
		</sourcecontrol>
		<triggers>
			<intervalTrigger seconds="60" buildCondition="IfModificationExists" />
		</triggers>
		<tasks>
			<msbuild>
  				<workingDirectory>C:\source\</workingDirectory>
  				<projectFile>matt.sln</projectFile>
				<targets>Build</targets>
				<buildArgs>/p:Configuration=Release</buildArgs>
				<logger>C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll</logger>
			</msbuild>
		</tasks>
	</project>
</cruisecontrol>
By the way, i've tried all sorts of combinations for the pathFilter with no success, the one here is just my attempt at excluding all ~sak files.

Any help would be very much appreciated - ccnet seems pretty cool but seriously lacking in documentation.

Thanks, Matt

ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Post by ian_sg » Tue Aug 28, 2007 8:30 am

We are using an exclusion path filter successfully, but because we have multiple source control blocks the layout is a bit different. What you have looks okay to me, but I'm not an expert on that feature of CruiseControl.NET.

Have you tried asking your question on the ccnet-user mailing list? They're usually quite responsive.
Ian Olsen
SourceGear

Post Reply