I want a dir that holds files which the different builds will reference. The contents should be the same on all slaves, and I'd like to specify the same thing as the path (e.g. "${FS_ROOT}/common") on all jobs on all slaves. I'd like to update this dir automatically.
Currently, I'm setting up 1. a slave-specific environment variable BASE[1], 2. a job whose workspace dir is set to be ${BASE}/extensions, that pulls a Mercurial repository down. (The repository contains Mercurial extensions we use in several of our builds.) 3. other jobs that, as needed, tell Mercurial to use one or more of those extensions. Mercurial requires an absolute path. I really don't care where this job puts its workspace, but I need to be able to reference it from other jobs with a local absolute path. I expect that the above approach will work, though it seems silly that I have to tell Jenkins what its filesystem root is, when it already knows it. [1] On Windows slaves, the BASE environment variable is already defined, but not on OSX slaves, so I define it just on them. Thank you, Todd Greer Marek Gimza said: > Do U want to have different builds sharing the same WORKSPACE or do U want a > dir that holds files which the different builds will reference? >> On Wed, Oct 17, 2012 at 3:46 PM, Todd Greer <tgr...@affinegy.com> wrote: >> Does anyone here happen to know how to find the remote fs root of a slave in >> Groovy? I'd like to do this so I can use EnvInject to put it in an >> environment variable, so I can use put some files there that all of my jobs >> can read.