Problems with 'Get Latest' from Vault

[ruben sassano]

Hi guys, we have recently purchased this tool to automate our build process, although it has significantly improve our daily task, we are sometimes getting bug down with some issues to do with getting the latest from our source control ‘Vault’.

We have been looking around in the forum and found few answers on the subject, so we have modified our ‘get’ step to run a batch step (as suggested) looking something like this:

C:\Program Files\SourceGear\Vault Client\vault.exe -host vault:XX -user <user> -password <pw> -repository "Default Repository" get "$/XXX" -merge overwrite -setfiletime modification -destpath "%BUILD_FOLDER%"

Since sometimes some of the latest versions weren’t still being retrieved, we added a few steps to delete the working folder and create a new one, thus, starting the ‘get’ operation with a totally empty folder, therefore there shouldn’t be any confusion at all with merges, but even though some of the latest file version are still ignored and the build is performed with old file version.

Could someone help on the subject, please??

Thanks.

[kinook]

This sounds like an issue for the SourceGear folks. The VBP Vault action invokes the Vault command-line tool to perform an action on a repository. You can provide the vault.exe command-line (along w/ the Vault client+server versions) to SourceGear to determine why this might be occurring and if there is a fix.