> What prevent you to get JDK8 on slave to run the remoting agent, but use >JDK installer to build your legacy JDK 1.1 application ?
In many cases this is possible. I don't think this is documented all that well though (I've done it once and it took me a while to get it right). I would imagine this is something that should be in an upgrade guide. If you can't run JDK8, then you get to run a legacy Jenkins install. > Sorry, but rhel5 is not something that we should care about, AFAIR it on >extended support. You can still use ancient jenkins version and ask RHEL >support to do patches for jenkins. RHEL6 and RHEL7 were released long >time ago - update your infra. I don't think we should be making sure NEW release cycles support RHEL5. It is in extended support, people in that environment should be comfortable dealing with tools from that era. That said, there are ways to make it work, but it shouldn't be blessed. > And it's simply not possible to update Jenkins (master) in isolation, >the remoting model requires that all slaves use similar JREs, and satisfy >the minimum requirements. But we shouldn't stay at Java6 forever. I am seeing a lot of hints at making some radical changes/improvements. Should we really be talking of a Jenkins2 and not expect people to auto-update to it? We could offer 1 or 2 more LTS on the 1.x track. - Thomas -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/D1372128.11495%25thomas.suckow%40pnnl.gov. For more options, visit https://groups.google.com/d/optout.
