Vault not detecting modifications correctly in CCNET

mcintyre321 · Post by **mcintyre321** » Tue May 15, 2007 2:36 am

We seem to be having a similar problem to http://support.sourcegear.com/viewtopic ... isecontrol. Our CruiseControl builds do not always kick off after a file is checked in and if they do, they do not always have a list of the files that were changed.

We are using 3.5.1, different servers for CCNET and SQL Server. CruiseControl runs under a logged in domain user set as a local admin on the CCNET server.

Here is our CCNET block.

Code: Select all

		<sourcecontrol type="vault" autoGetSource="true" applyLabel="false">
			<executable>&vault.executable;</executable>
			<username>&vault.username;</username>
			<password>&vault.password;</password>
			<host>&vault.host;</host>
			<repository>&vault.repository;</repository>
			<ssl>&vault.SSL;</ssl>
			<folder>$/Dsi/DatabaseUpdater</folder>
			<useWorkingDirectory>&vault.useWorkingDirectory;</useWorkingDirectory>
			<workingDirectory>&ccnet.projectsDirectory;\dev\DatabaseUpdater</workingDirectory>
			<cleanCopy>&vault.cleanCopy;</cleanCopy>
			<setFileTime>&vault.setFileTime;</setFileTime>
		</sourcecontrol>

Any ideas on how to fix this? thanks

ian_sg · Post by **ian_sg** » Tue May 15, 2007 8:30 am

The current implementation requires that the CCNet server and SQL Server machines' clocks be precisely synchronized. If you have lots of checkins and poll for changes frequently, even slight discrepancies in the clocks can cause this problem. I acknowledge this is a pain.

Fixing it required a whole new type of history query in Vault, which is set to be included in the next major release.

mcintyre321 · Post by **mcintyre321** » Tue May 15, 2007 10:08 am

i compared the two server clocks by opening two remote desktops at the same time - they match to less than a second (i think they are synched to the same clock). Is this still not accurate enough?

oh and as a gold supprt user, will we be eligible for a free upgrade?