Jenkins is running on a master machine, which has other slaves, but
is also used as a build machine in a Configuration Matrix, by selecting
master.

The jenkins setup information is under $JENKINS_HOME as is the
triggering checkout.  That is chosen to be a a fairly stable
file system.

But then I would like the master, when used as a build slave, to
build in a different file system.

Some solutions I have thought of:

Create a second jenkins user on the master, and create a slave to that
second user name.  (I prefer to keep it all under the one jenkins user.)

Soft link the second file system into the jenkins workspace under
workspace/<project>/OS/master, but then I have to create that link
for every project.

Is there a simpler way?

Thx...John Cary

Reply via email to