I know projects that uses ancient distros and the root problem is that they didn’t schedule/plan upgrades in time at all. They don’t want to do it and it easy for them to slow down any projects they want. I think CloudBees will be a good company for doing payed support for ancient platforms. I know already some plugins that require 1.7 and maintainers doesn’t want to waste their life time with dealing somebody internal company issues. Btw some people still silently patches 1.509.X for their needs :)
> On Mar 24, 2015, at 23:57, nicolas de loof <[email protected]> wrote: > > 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 ? > > 2015-03-24 21:57 GMT+01:00 Daniel Beck <[email protected] > <mailto:[email protected]>>: > > On 24.03.2015, at 20:53, Kanstantsin Shautsou <[email protected] > <mailto:[email protected]>> wrote: > > > 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. > > The problem with the Java version used to run Jenkins is that it needs to be > available on whatever box your builds run on. > > It's nice if you're only building products using the latest hype technology, > and discard them as soon as they're done, or upgrade the technology stack in > every iteration, but there are *many* companies that still need to maintain > products originally developed a decade or more ago, and the tools to build > them are just as old, and wouldn't properly run on current systems. > > 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. > > > Ok, s/we/imho/ . Btw, there should be somewhere statistics. Let’s check how > > many RHEL5 installation jenkins has. > > If you're referring to the anonymous usage statistics, we only know that > they're running Linux, and the CPU architecture (os.name <http://os.name/> > and os.arch). > > And again, it's likely not the "installations" of Jenkins (i.e. master) that > are the problem, but the build nodes. > > -- > 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] > <mailto:jenkinsci-dev%[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/25005053-52C1-4F40-B722-2A69E5A64F4D%40beckweb.net > > <https://groups.google.com/d/msgid/jenkinsci-dev/25005053-52C1-4F40-B722-2A69E5A64F4D%40beckweb.net>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/sw_WepGw0Pk/unsubscribe > <https://groups.google.com/d/topic/jenkinsci-dev/sw_WepGw0Pk/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzmtvFmMnMki7q6H-0NDLmsQVjuzuC2xexvc0hb204iCaQ%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzmtvFmMnMki7q6H-0NDLmsQVjuzuC2xexvc0hb204iCaQ%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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/FBDD4CEA-CF9E-4673-93B8-A94A6708B259%40gmail.com. For more options, visit https://groups.google.com/d/optout.
