Launching agents via SSH is a reasonable approach also for normalizing configuration of agents across multiple platforms.
My company's build environment uses multiple Linux flavours, a Windows client (configured using OpenSSH), and a NonStop - all as agents, with a Controller running under Ubuntu. Each host has a specific jenkins user its own unique key pair (with passphrases) to cut down on accidental configuration errors. Hope this helps. Randall On Wednesday, December 5, 2018 at 6:26:44 AM UTC-5, Jeff Thompson wrote: > > For situations where it is reasonable, I agree with Slide’s > recommendation: #1 Launch agents via ssh > > It’s a good implementation, fairly straightforward, and I think it leads > to better reliability and fewer broken connections. I don’t have any data > on that, though, so I’d also love to hear from others with experience using > the different mechanisms. > > Jeff Thompson > > On Dec 4, 2018, at 1:48 PM, Slide <[email protected] <javascript:>> > wrote: > > FYI, even though the term is used in some places in the docs and code > (because it's hard to change everything), "agent" is the requested term > instead of "slave". That being said, I prefer the "Launch agents via ssh", > I've never had a problem with reconnection after a reboot of the agent > computer. > > On Tue, Dec 4, 2018 at 1:44 PM <[email protected] <javascript:>> wrote: > >> Any inputs on this please? >> >> On Tuesday, December 4, 2018 at 9:03:37 AM UTC-5, [email protected] >> wrote: >>> >>> What is the best or standard way to configure a Linux slave to the >>> Master? These are the options that comes while we try to do the >>> configuration >>> >>> 1. Launch agent agents via ssh >>> 2. Launch agent via Java Web Start >>> 3. Launch agent via execution of command on master >>> 4. Let Jenkins control this Windows slave as a Windows machine >>> >>> Our requirement is if the Slave VM reboots, we want the Jenkins service >>> to start automatically and the slave to connect to master without any >>> interruption. Please suggest. >>> >> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/415b5e85-89ca-4461-8bd9-b8450aacfeeb%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/415b5e85-89ca-4461-8bd9-b8450aacfeeb%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Website: http://earl-of-code.com > > -- > 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVf3jygh7vmqSrBbf079FmKnCOFgO7H1W3xR%3DeLoSE4bnw%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVf3jygh7vmqSrBbf079FmKnCOFgO7H1W3xR%3DeLoSE4bnw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e3e132b7-e022-419d-a98e-e5f701097e91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
