Please excuse me if this has been addressed before but I couldn't find anything on this with a quick search. We're using Vault 3.1.6.
Can we configure Vault to do a Get Latest Version (on a file) to some other working folder every time a user checks in a file? If not, is there some way to trap the File Check In event (perhaps by using the Vault Client API)?
We need to maintain the source code files on disk (for compiling) in a central location without causing programmers to perform extra steps (e.g. change the working folder to the central location then do a Get Latest Version) every time they check in a file.
Any help and/or guidance would be much appreciated.
TIA
Check In Event
Moderator: SourceGear
You could use Shadow Folders.
A shadow folder is a local folder that contains the contents of a repository folder, and is kept up-to-date in the shadow folder by the Vault server as changes are applied to repository folder.
For details, see Vault Admin Tool Help->Repository Options->Configure Shadow Folders.
Another option, if you are doing builds, is to use the Vault Command Line Client to do a get to a non-working folder. Many of our users write a script that incorporates the CLC, to automate this.
A shadow folder is a local folder that contains the contents of a repository folder, and is kept up-to-date in the shadow folder by the Vault server as changes are applied to repository folder.
For details, see Vault Admin Tool Help->Repository Options->Configure Shadow Folders.
Another option, if you are doing builds, is to use the Vault Command Line Client to do a get to a non-working folder. Many of our users write a script that incorporates the CLC, to automate this.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager