Hi...
We've got an older version of Vault (3.1.9.3798) so this may have changed, but I've been a little perplexed on how the Vault GET command seems to be detecting repository changes. I was hoping a little light may be shed on it.
We have a scripted build system that wants to pull out specific subfolders out of a repo root and build the projects therein. I'm trying to upgrade the script not to bother doing the build if it doesn't detect any changes.
Like most places, we branch our whole tree when we cut a release, so our repo has the $/development tip, plus $/release.xxx, $/release.yyy, etc.
I seem to find the following things:
1) If you run SETWORKINGFOLDER on a branch, subsequent GET operations will fetch all the files whether changed or not.
2) Using GET to a subfolder(e.g. with $/development set to D:\Dev, GET $development/foo will dump things in D:\Dev\foo) all files are fetched whether they've been changed or not. But doing GET $/development, it will only fetch files if changed.
The latter spawns a couple of questions for me:
1) I didn't see any .svn-like subdirs in the local copy; how is Vault telling that nothing changed when I do a GET $/development and
2) Why can't it apply the same logic to a GET of a subfolder?
Thanks
Mark
Vault and change detection
Moderator: SourceGear