On 24.03.2015, at 20:53, Kanstantsin Shautsou <kanstantsin....@gmail.com> 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 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit 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.
