Re: SSH vs java web start for windows slave and Linux master in jenkins

ssh lets you only use resources while you need that node. (unless you chose "Use this node as much as possible") If I remember correctly, an agent can use around 80 MB of RAM. If your machine is quite resource-constrained, such as a Raspberry Pi that you use only sometimes for building for

Re: SSH vs java web start for windows slave and Linux master in jenkins

Another interesting bit of info which I didn't notice until now. Even getting the JNLP slave to run as a Windows service requires .Net 3.5, (https://wiki.jenkins-ci.org/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines). On Tuesday, April 12, 2016 at 12:58:12 AM UTC-7,

Re: SSH vs java web start for windows slave and Linux master in jenkins

These instructions (https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29) specify .Net 2.0. On my Windows 2012 VM with only .Net 4, I couldn't get the slave service to

Re: SSH vs java web start for windows slave and Linux master in jenkins

It should run just fine on newer versions of the .NET framework. I didn't see anything in the code that was 3.5 specific. On Mon, Apr 11, 2016 at 7:16 PM Wei-min Lee wrote: > I'm also curious about running the window slave as a service which > requires .Net 3.5 in that

Re: SSH vs java web start for windows slave and Linux master in jenkins

I'm also curious about running the window slave as a service which requires .Net 3.5 in that Microsoft is looking to end support for 3.5. Would there be an update that supports higher versions of .Net or should I be looking at converting my Windows slaves to launch via java web start - seeing

Re: SSH vs java web start for windows slave and Linux master in jenkins

Thanks Stephen On Tuesday, April 5, 2016 at 3:42:25 PM UTC+5:30, Stephen Connolly wrote: > > SSH is encrypted, but uses Blocking I/O (unless you use the CloudBees > proprietary NIO SSH Slave connector) so scalability can be limited. > > JNLPAgentProtocol2 is unencrypted and uses Non-Blocking

Re: SSH vs java web start for windows slave and Linux master in jenkins

SSH is encrypted, but uses Blocking I/O (unless you use the CloudBees proprietary NIO SSH Slave connector) so scalability can be limited. JNLPAgentProtocol2 is unencrypted and uses Non-Blocking I/O, so you get back-pressure when the server is under load, but good scalability. JNLPAgentProtocol3

Re: SSH vs java web start for windows slave and Linux master in jenkins

Thanks for the reply jpd4nt. for anybody - any other advantages between these two protocols. Thank, Naveen On Monday, April 4, 2016 at 10:43:18 PM UTC+5:30, jpd4nt wrote: > > Hi Naveen. > > I find ssh option more robust because our Jenkins master is behind a load > balancer so the web start

Re: SSH vs java web start for windows slave and Linux master in jenkins

Hi Naveen. I find ssh option more robust because our Jenkins master is behind a load balancer so the web start has to go through that, we use AWS ELB and sometimes the connection breaks. Also with a fix master its easier to set the access rules that for a slave ringing home back to the

SSH vs java web start for windows slave and Linux master in jenkins

Hello, I am configuring jenkins from linux to windows, with windows as slave. I have configured in both protocols. I see java web start very easy to configure the master slave. But while configuring the windows slave through SSH it is more complicated compared to java web start. I wanted to