In the end, this is just annoying, but I have two separate volumes on my build machine. 80GB volume for OS and framework build binaries (VC++ runtime, SDKs, etc.) and a separate volume for source code, build artifacts, etc.
I would like to have Jenkins use a path such as L:\jenkins\<JobName>\workspace and have it properly update the Perforce workspace. L:\Jenkins ==> Would be some kind of variable set per slave jenkins build machine <JobName> ==> Obviously :) "workspace" ==> Could be any variation of a relative path to tack onto the end of the former pieces (ex. builds\p4workspace\1\etc\etc\etc)\ Can this easily be done with the Perforce plugin, or am I barking up the wrong tree? Regards, Stephen
