The cache is what Vault uses for determining what changes have been made to a file, and it watches the working folder. Does your build machine need to check in any changes? If not, then the solution is to not set a working folder at all, or, if it's already set, to remove the working folder association. Then a Get can be performed to any location and the build performed with no cache created. The cache only deals with a working folder.
If you are having problems performing the Get without the working folder, then you can set it, but don't build from it. Still Get to a different location and leave the working folder empty.
No Cache at all
Moderator: SourceGear