On Mon, Feb 13, 2012 at 2:52 PM, John R. Cary <[email protected]> wrote:
> On 2/7/2012 10:35 AM, Les Mikesell wrote: > >> On Tue, Feb 7, 2012 at 10:57 AM, John R. Cary<[email protected]> wrote: >> >>> 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.) >>> >> Why would you need a different user for this? Can't you just specify >> the 'remote FS root' for the slave to be where you want it as long as >> jenkins can write there? >> >> > > So are you saying that it would be a slave, e.g., > launched by ssh, but going back to the same machine? > There is probably more than one way to do it, but I'd try treating it like any other remote slave first. It is always best to design slaves to be more or less interchangeable and scalable by adding groups with the same labels. I don't see why anything should care that the ssh target is the same as the master. -- Les Mikesell [email protected]
