Vault 4 Checkout

FinalBuilder Discussion
1

Vault 4's command line ABSOLUTELY allows wildcards now but when I try to add an action inFinalBuilder to checkout recursively something liek *.res I get an error saying Vault doesn't support wildcards.  What gives?

2

Hi Ed,

Thanks for pointing this out. This is a hangover from Vault 3, where the wildcard had to be specified under a particular command line option.

At the moment, you can work around it by putting the wildcard into the "Wildcard" field further down that property page. However, I'll modify the property page so you can add wildcards to the main file list as well (you are correct that they will work in Vault 4.)

_However_, if you want recursion then you actually want to use the specific Wildcard field anyhow, because putting wildcards into the standard "File List" section will not perform recursive matching.

Regards,

Angus

3

Angus,

thanks for the quick quick reply. You are correct. I am looking for recursive wildcard checkouts. Is there a way to specify partical filenames? For instance, I want to recursively checkout ONLY my resource files. I specified *.res in the 'Specify Wildcard' but that didn't work.

4

Angus,

I did a little digging on Source Gears support forum and foudn something.

The command FinalBuilder is executing based on my settings is: (edited for security)

checkout -user "__" -password "-----" -host "myrepositoy.com" -repository "Someplace" -exclusive -wildcard *.res "$/Trunk/Common"

this command ends up checking out EVERYTHING in the Common project folder.

However, if I change the command and execute this from a command prompt:

Vault.exe checkout -user "__" -password "-----" -host "myrepositoy.com" -repository "Someplace" -exclusive -wildcard *.res  "$/Delphi_50/Trunk/**/*.res"

 It works like a champ. The Source Gear forum I was looking at is at http://support.sourcegear.com/viewtopic.php?t=8126&highlight=wildcard+checkout

 

 

5

Hi Ed,

I see. Thanks for pointing this out. When I was testing I must have overlooked that I was checking everything out, not just *.res.

I guess the wildcard option must be totally non-functional now. It's tiring trying to keep up with all the changes in the Vault command line syntax!

For now, the best solution when using FB is to enter the file name as "**/*.res". Then everything should just work.

You will, however, need the latest test build of FinalBuilder, where we've just updated so it lets you use Wildcards in the file name list for Vault 4:

https://www.finalbuilder.com/downloads/finalbuilder/550/FB550_422.exe

Please let us know how you go. We'll try to think of a more permanent solution to this problem (probably we can automatically convert the -wildcard option to the Nant-style equivalent when using Vault 4.)


Regards,

Angus

6

Angus,
outstanding! I downloaded the update and did what you said. It works perfectly. Thank you very much!