Building solution (vs.net2003) with Vault

[Domagoj.Kovac]

I'm using VSS and "BuildIt" to automate builds with VSS. Since we are considering moving to Vault, I'm wondering if there is present tool or how-to that explains how to automate builds with Vault.

Thx,
Domagoj

[dan]

Vault has a command line client and a client side API that can both be used to automated builds. We use the command line client internally.

Help is available on the command line client by typing 'vault help'. The client API is not documented very well, but one of our developers has a blog on how to get started with it at: http://weblogs.asp.net/Jeremy_Sheeley/

[Domagoj Kovac]

... (took a look at vault help) - was hoping to example of how to chekc out solution (vs.net 2003) build it, label it, and copy it to some network share. Looks like ill have some reading to do

Anyway, i'm currenty in process of testing internally on our project Vault, and im.... i cant find words to describe it! Refreshing project on local LAN (100MB) took with VSS 3.5-7.7 minutes (depending on weather and what is playing on radio), and with Vault - around 10 seconds!!!?!?! I'm speachless.... If I only make this build process working soon so I can get back to work (deadlines, deadlines), ill be one happy customer ))

Domagoj Kovac

[Don Thimsen]

Domagoj,

As you start playing with the command line interface, you'll find the performance not comparable to the VSS command interface. In fact, you'll find that every vault command takes at least a few seconds to perform. If you've done install scripts using VSS, it will not look good at first.

After playing around and reading the support forum, you'll probably end up using a BATCH request. Using the BATCH command significantly improved our build scripts. It's still not as fast as VSS, but reasonable...

Here's an example where a single BATCH command extracts a bunch of files. Also, I believe you can comment out the REMEMBERLOGIN command after the first time you execute the script.

Don


echo GETWILDCARD -makewritable -destpath "c:/source/difr41/ispf" $/difr41/ispf * > #vault.dat
echo GETWILDCARD -makewritable -destpath "c:/source/extr41/ispf" $/extr41/ispf * >> #vault.dat
echo GETWILDCARD -makewritable -destpath "c:/source/monr41/ispf" $/monr41/ispf * >> #vault.dat
echo GETWILDCARD -makewritable -destpath "c:/source/dslr41/ispf" $/dslr41/ispf * >> #vault.dat
echo GETWILDCARD -makewritable -destpath "c:/source/sccr41/instlib" $/sccr41/instlib * >> #vault.dat
echo GET -makewritable -destpath "c:/source/sccr41/instlib" $/sccr41/relinfo.txt >> #vault.dat
echo GETWILDCARD -makewritable -destpath "c:/source/difr41/samplib" $/difr41/samplib * >> #vault.dat
echo GETWILDCARD -makewritable -destpath "c:/source/extr41/samplib" $/extr41/samplib * >> #vault.dat
echo GETWILDCARD -makewritable -destpath "c:/source/monr41/samplib" $/monr41/samplib * >> #vault.dat
echo GETWILDCARD -makewritable -destpath "c:/source/dslr41/samplib" $/dslr41/samplib * >> #vault.dat
echo GETWILDCARD -makewritable -destpath "c:/source/accr41/samplib" $/accr41/samplib * >> #vault.dat
echo GET -makewritable -destpath "c:/source/sccr41/scczaps" $/difr41/difzaps.asm >> #vault.dat
echo GET -makewritable -destpath "c:/source/sccr41/scczaps" $/extr41/extzaps.asm >> #vault.dat
echo GET -makewritable -destpath "c:/source/sccr41/scczaps" $/accr41/acczaps.asm >> #vault.dat
echo GET -makewritable -destpath "c:/source/sccr41/scczaps" $/monr41/monzaps.asm >> #vault.dat
echo GET -makewritable -destpath "c:/source/sccr41/scczaps" $/dslr41/dslzaps.asm >> #vault.dat
echo GET -destpath "c:/source/sccr41" $/sccr41/slbuild.dat >> #vault.dat
cd "\Program Files\SourceGear\Vault Client\"
vault REMEMBERLOGIN -host vault.dts -user uuuuu -password ppppp -repository "Default Repository" > nul
vault BATCH c:\source\sccr41\#vault.dat > nul

[Domagoj Kovač]

Thx, think this will get me started just nicely

Domagoj Kovač