Shared working folder

[guilmori]

Using Vault Client 4.1.4.

Our developers work locally and all have their own working folder.
When the code is ready to go through QA, we put it on a shared drive.
My question: is their any problem if many QA users have their Vault repository path set to the same working folder (the shared drive) ?
The QA team would never do any check-out, only Get Latest operations.
Would the Vault cache be shared between all QA users ?

Thanks,
Guillaume

[Beth]

The cache is different for each user login. If QA is never checking in changes nor looking at the statuses, then they are probably fine all pointing to the same working folder.

You may want to check out shadow folders though. That's an easy way to get the latest code to a disk location without QA needing a Vault GUI client at all. Shadow folders automatically update, but there is a way to control that through the use of pinning. You would create a share of your code, but pin it. When new code needs to go to the location on disk for QA to look at, one would just unpin and repin the folder.
$
|---Project1
|---------project 1 file and folders
|---------more project 1 file and folders
|---Project1 QA share (Place pin here to stop changes going from Project1 to QA. Unpin when ready for all new changes.)
|---------shared project 1 file and folders
|---------shared more project 1 file and folders

[guilmori]

Could all QA users log into Vault with the same user, and put the cache files in the working folder ?

[Beth]

You would have to talk to our sales department about licensing for that. It technically can be done, but you will want to make sure you're covered, otherwise it would be a license violation. Our sales department can be reached by emailing sgstore at sourcegear.com, and you will want to include a full explanation.

If all QA are looking at the same disk location and not doing anything with Vault, you might consider designating one QA member to have access to perform Gets. Or you could write a script using our command-line client that can be automatically kicked off to perform a Get.