By the way, i also noticed when using the built in ssh plugin, the slaves are launched by the anonymous account even if i created them with a specific admin user.
Le jeudi 3 octobre 2013 10:26:11 UTC+2, Raouf a écrit : > > What i don't understand is that my scripts worked well when i was using > 1.456, i could use as many test slaves as i wanted without having conflicts > with the main slaves > > The issue occurs only since i moved my test instances to a 1.5xx version, > so i'd like to know what happened exactely, and how to get things back to > normal. > > Regards, > Raouf. > > Le mardi 1 octobre 2013 17:42:12 UTC+2, LesMikesell a écrit : >> >> On Tue, Oct 1, 2013 at 10:18 AM, Raouf Abdelhamid >> <[email protected]> wrote: >> > Actually i did try it and it worked well. But i don't know exactly wich >> > slave jar was lanched, and i can't just abandon the scripts since >> they're >> > doing some other stuff (logging, restarting on fail ...etc.) >> >> The built in support should take care of getting the right jar in the >> right place for you - and probably doing everything else jenkins >> needs... >> >> In any case, I'd run under different users with different home >> directories so the jars and other files don't clobber each other. >> >> -- >> Les Mikesell >> [email protected] >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
