I've got a new Jenkins master (1.622) running on CentOS 6.6 x86_64, tomcat 8, java 1.8. All working ok.
I've just had a request for a build on an old Linux slave - Red Hat 4 with Java 1.6 (32 bit). Yes, I know it's obsolete, and it ought to be upgraded to plug all the security holes - but that's what I need. Normally we connect to Linux slaves via ssh, however I know that these are basically incompatible. slave.jar needs jdk 1.7, at least and that won't run properly on Red Hat 4 because of glibc library. However it WILL connect using JNLP whilst launching the interactive java Jenkins Remoting Agent, but NOT whilst running the jnlp command line command from the slave. I can understand why the command line launch doesn't work with the java version incompatibilities. An old version of slave.jar from an old Jenkins master seems to work ok, and may be 'good-enough', but how robust is it? Are there any listings of version compatibilities? Does anyone have any ideas on how to get an old Linux machine enslaved to a new Jenkins master? Any alternative connection techniques? I guess the obvious solution is just to use an old Jenkins master which is compatible… -- 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/c65091cb-6ec5-4c56-b531-efab07a4a8d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
