Does anyone know if the <vaultget> task will automatically grab everything, or if, similar to the vault client, it only actually downloads files that have changed? I don't seem to see any <getoptions> that might control this behavior.
Reason I ask is that I have a very large project here (file count and size-wise) and it takes nearly an hour to download the entire set of assets to a blank working folder, but it also seems to take a long time if the latest files already exist in that folder. I'm curious if it's worth my time to experiment whether it's faster to nuke my whole local source folder and re-fetch all the files for each build, vs. keeping the soure folder between builds and have to do a bunch of version comparisons before fetching only the changed files. I'm starting to think the version comparison step is consuming the bulk of the time whether the files exist in the working folder or not and that I'm just plain stuck with a 1hr build time. That would suck.
Either way, it would be useful to know if my assumption that <vaultget> is only retreiving changed files is even accurate. If it's getting the whole project anyway, then I'll have to deal with it, or find a nother way to deploy the static content in my project.
Thanks in advance.
vault nant integration question
Moderator: SourceGear
Re: vault nant integration question
Your assumption is correct, vaultget does a working folder get, which will only download changed files.
Re: vault nant integration question
Thanks for clarifying that.
Re: vault nant integration question
Let us know if you have further questions.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager