Thanks Jerome and Slide. Seems like SSH on Windows is the new way to go (it 
feels so strange to say these words, "ssh on Windows"...) !
Thanks

Le lundi 23 novembre 2020 à 18:22:19 UTC+1, slide a écrit :

> I would highly recommend switching to using SSH for Windows agents. The 
> Win32-OpenSSH implementation from MS is supported from Windows 7 on (though 
> Windows 7 is EOL). This makes it easier to maintain your agents because 
> both the Windows and Linux agents are using the same mechanism. I've been 
> meaning to write a blog post about this, but haven't had the time to. I 
> switched all of my agents over to SSH last year and it has been working 
> very well for me.
>
> Regards,
>
> Alex
>
> On Mon, Nov 23, 2020 at 7:12 AM Jérôme Godbout <godb...@amotus.ca> wrote:
>
>> Hi, 
>>
>>  
>>
>> if you are using Windows 10 for your slave, just enable the Windows 
>> Features for OpenSSH client and server. This would make it just like a 
>> Linux node. Make sure to put your Java install into a path without spaces 
>> (I think the fix is in the pipeline depending of the Jenkins version you 
>> have).
>>
>> That make it easier as it do just like linux to log in and seem more safe 
>> to me, you just put the credentials into the Jenkins master for the ssh key.
>>
>>  
>>
>>  
>>
>>
>> une compagnie  
>>
>> RAPPROCHEZ LA DISTANCE
>>
>> *Jérôme Godbout*
>> Développeur Logiciel Sénior / 
>> Senior Software Developer
>>
>> *p:* +1 (418) 800-1073 ext.:109
>>
>> amotus.ca <http://www.amotus-solutions.com/>
>> statum-iot.com
>>
>> <https://www.facebook.com/LesSolutionsAmotus/>  
>> <https://www.linkedin.com/company/amotus-solutions/>  
>> <https://twitter.com/AmotusSolutions>  
>> <https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
>>
>> *COVID-19 : we are glad to inform you that Amotus 
>> <https://www.amotus-solutions.com/> are up and running with limited impact 
>> on our performance. We will keep you informed of any changes as they occur.*
>>
>> *COVID-19 : nous sommes fiers d’informer nos collaborateurs que Amotus 
>> opèrent adéquatement et que l’impact sur notre productivité est minimisé. 
>> Nous vous tiendrons au courant de tout changement.*
>>
>>  
>>
>> *From:* jenkins...@googlegroups.com <jenkins...@googlegroups.com> *On 
>> Behalf Of *Francois Marot
>> *Sent:* November 23, 2020 6:24 AM
>> *To:* Jenkins Users <jenkins...@googlegroups.com>
>> *Subject:* Recommended way to setup a windows agent nowadays ?
>>
>>  
>>
>>  
>>
>> Hello Jenkins users,
>>
>>  
>>
>> I'm in the process of upgrading my Jenkins installation. My Jenkins Linux 
>> master has been updated with the latest LTS but not the agents for the 
>> moment.
>>
>> I'm wondering how to update the Windows agents.
>>
>> For exemple: one outputs the following logs:
>> > "WARNING: Remoting version is older than a minimum required one (3.14). 
>> Connection will not be rejected, but the compatibility is NOT guaranteed"
>>
>>  
>>
>> I think it was configured with JavaWebStart and runs as a service but I 
>> also think that Java Web Start is more or less deprecated in Java 8+.
>>
>> On the other hand, configuring with the other way (WMI I think) leads to 
>> the following help message in Jenkins master:
>> > " This launch method relies on DCOM and is often associated with subtle 
>> problems 
>> <https://github.com/jenkinsci/windows-slaves-plugin/blob/master/docs/troubleshooting.adoc>.
>>  
>> Consider using *Launch agents using Java Web Start* instead "
>>
>>  
>>
>> So my question is: what is the preffered way to setup a *windows* agent 
>> connected to a Linux master nowadays ? Isn't JNLP deprecated ? Is there an 
>> up to date definitive doc ?
>>
>>  
>>
>> Thanks
>>
>> -- 
>> 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 jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/6dd94526-10df-4c77-b734-dda9d7308e54n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/6dd94526-10df-4c77-b734-dda9d7308e54n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> -- 
>> 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 jenkinsci-use...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/QB1PR01MB384470D344193ECCCC3DA4B3CDFC0%40QB1PR01MB3844.CANPRD01.PROD.OUTLOOK.COM
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/QB1PR01MB384470D344193ECCCC3DA4B3CDFC0%40QB1PR01MB3844.CANPRD01.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> -- 
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/994f6f26-25a4-421e-9df5-8f8aa4b74e9cn%40googlegroups.com.

Reply via email to