Exclamation mark placed in file when getting

[dmurty]

Hello,

We are using sourcegear vault version 4.1.4.18402 with cruisecontrol.net version 1.4.4.83. We downloaded the Vault CruiseControl.NET plugin for vault 4.1.4 and the sourcegear vault config in the ccnet.config is as follows:
<sourcecontrol type="vaultplugin" autoGetSource="true" applyLabel="false" cleanCopy="true">
<username>admin</username>
<password><our password></password>
<host>csserver2.2synergy.local</host>
<repository>HealthCare Assistant</repository>
<folder>$/1 - Current Development</folder>
<ssl>true</ssl>
<useWorkingDirectory>true</useWorkingDirectory>
<workingDirectory>D:\install</workingDirectory>
</sourcecontrol>

One file that is a vb6 form file gets an exclamation point added to it when we get latest. If we get the file on the same machine using the vault gui client it does not place the exclamation point. Also it did not start doing this until we changed the cleanCopy property to "true".

When we show the differences on the file the working file has an exclamation point rather than a space which causes our project not to compile.

Please Help!


Thanks,
Damien

[dmurty]

I did some debugging and changing the cleanCopy value does not change anything. If we get from the vault gui client or from the vault command line then it gets the file without adding the exclamation point. It seems like it is from the vaultplugin for cc.net. I am now changing the ccnet.config to use the vault sourcecontrol. Hopes this helps.

Thanks,
Damien

[jeremy_sg]

Damien,

One of the most common bits of confusion when trying to have CC.Net and the Vault GUI on the same machine and working on the same folders is that they have to be using the same Windows user account and the same Vault user account. Is that the case here?

If you load the Vault GUI client, what's the status of the problem file?

[dmurty]

The Vault GUI and CC.net are using the same vault user, but I am not sure about the same windows user account. How can I tell which windows user that cc.net is using. We have cc.net setup to run as a service, so I think that it would be using the local system user. After cc.net gets all the files if we open up the vault gui all files have a status of renegade and the only difference for the problem file is that the repository has a space and the working version has an exclamation point instead of the space.

Should I change the service to use the same windows user account as we do when we RDP to the machine?

Thanks,
Damien

[jeremy_sg]

Damien,

You didn't answer this question: If you load the Vault GUI client, what's the status of the problem file?

The answer is important, because it can tell us what the cause of the exclamation is. I'd like to deal with that before you change your CC.Net setup entirely.

[dmurty]

I guess I don't know what you mean by the status of the problem file. If I open the vault gui the status of the file is renegade. If I show differences the only difference is the exclamation point. Is that what you want?

[jeremy_sg]

That's great.

Renegade means "This file is writable". If you Get Latest on the file with the Overwrite setting, it should go back to a blank status, and you should be fine.

[dmurty]

OK,

But everytime we get the file from cc.net it gets it with the exclamation point in the file. If we have to manually get and overwrite the file using the vault gui, that breaks our continous build.

Thanks,

[jeremy_sg]

Something is marking the file writable, possibly during your build. Can you check your build script for what could be doing that?

Since you've got cleanCopy=true, then the file is probably getting set as writable after the get (I can't think of any reason that the file would be different from all of the others).

Also, perhaps you can sprinkle some delays in your build script to check the status of that file at several points during your build (at startup, for example).