Multiple users on a shared Build machine

[JohnASchmitz]

Hi,

We have already changed a number of our development procedures to accomodate the way that Vault caches file status information (details provided on request). However, we've run into another problem. We have a single build machine that runs automated builds of our products. While the vast majority of the development takes place on developers' machines, when there is a problem in the build, we go to the build machine to investigate, and will usually check in changes there. I noticed this morning when I did this that the status of all the files was Unknown. I assume that this is because all of the previous work had been done by another developer who was changing the build procedure over to use Vault.

Is this developer's copy of Vault now going to see any files that I work on as "Unknown"? Is there something that will update this status? Basically, is there a way for several of us to work on the build machine's copy of the source without confusing Vault?

Thanks,
John

[lbauer]

Client-side cache files and baseline files for a working folder are generally stored in the Windows user's Local Settings->App Data folder, and under that, by Vault user login. So different users with the same working folder will get inconsistent file status information.

One option might be to have the Vault Client store the file data in the working folder. This setting is in the Vault GUI Client under Tools->Options->Local Files->Cache Location->Store Working Folder State/Baseline files. Each user would need to use that setting when checking in files on the Build machine.

After changing the setting, they would need to do a Get Latest to recreate the baselines.