Re: [DISCUSS] Time for Jenkins to require Java 8 to run

PR for Java 8 baseline bump is up at https://github.com/jenkinsci/jenkins/pull/2802 Reviews much welcome. Thanks! 2017-01-16 9:26 GMT+01:00 Baptiste Mathus : > FYI, Announcement PR is up https://github.com/jenkins- > infra/jenkins.io/pull/545 > > 2017-01-03 22:45 GMT+01:00

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Just a standalone topic. Migration to Java 8 may likely break use-cases with Maven plugin when it uses Java 7 (and it WILL break it if we migrate remoting). There is a valid question about it here

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

FYI, Announcement PR is up https://github.com/jenkins-infra/jenkins.io/pull/545 2017-01-03 22:45 GMT+01:00 Baptiste Mathus : > Follow-up: https://github.com/jenkinsci/jenkins/pull/2698 is the PR to > add Windows build to the core. > > Thanks Alex! > > Review welcome to speed up

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Follow-up: https://github.com/jenkinsci/jenkins/pull/2698 is the PR to add Windows build to the core. Thanks Alex! Review welcome to speed up the process and merge hopefully soon. 2016-12-21 17:24 GMT+01:00 Baptiste Mathus : > Great, Alex \o/. > > Tyler had played a bit the

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Great, Alex \o/. Tyler had played a bit the informer about it on you, but couldn't find this on the existing PRs and didn't ask you afterwards. ;-) Then mostly fixing tests is left TBD IIUC. 2016-12-21 15:43 GMT+01:00 Slide : > I have a PR almost ready for Jenkinsfile to

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

OK, sounds like a plan. IIUC think we have an agreement. > So I am +1k on switching to JDK8 with the proviso that at the time the call is made to do that the code is building and passing tests correctly. So I propose we do three things: 1) Start the process proposed by Oliver, Day 0 will be

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I have a PR almost ready for Jenkinsfile to build on Windows and Linux. On Wed, Dec 21, 2016 at 7:42 AM Baptiste Mathus wrote: > OK, sounds like a plan. IIUC think we have an agreement. > > > So I am +1k on switching to JDK8 with the proviso that at the time the > call is made

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Sunday, December 18, 2016 at 9:11:12 PM UTC, Baptiste Mathus wrote: > > @James, so can you please give us an update of the current state about > this? > > My understanding is the following below, can you confirm/complete? > > 2016-12-07 13:01 GMT+01:00 James Nord : > >>

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

@James, so can you please give us an update of the current state about this? My understanding is the following below, can you confirm/complete? 2016-12-07 13:01 GMT+01:00 James Nord : > I am -1000 on this. > > The code does not pass tests on windows. Using java8 you force

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I took a small peek at this (I commented this on the issue you filed as well) and found that 8 of the 9 errors are probably due to symlink creation. By default only certain accounts can create symlinks on Windows. Jenkins warns about this and gives you the information on how to add your user

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Wednesday, December 7, 2016 at 7:33:58 PM UTC, James Nord wrote: > > > > On Wednesday, December 7, 2016 at 2:23:33 PM UTC, Jesse Glick wrote: >> >> On Wed, Dec 7, 2016 at 7:01 AM, James Nord wrote: >> > The code does not pass tests on windows. Using java8 you force me

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Wednesday, December 7, 2016 at 2:23:33 PM UTC, Jesse Glick wrote: > > On Wed, Dec 7, 2016 at 7:01 AM, James Nord > wrote: > > The code does not pass tests on windows. Using java8 you force me to > use a > > Virtual machine > > Can you be more specific about the

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I had added this subject to the gov meeting for tonight since there hasn't been strong pushback for 6 weeks. But as I will most likely not be able to be present (in 13' now), I don't know if this should be kept or not in the agenda. I think that the plan proposed by Oliver would still work

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Wed, Dec 7, 2016 at 7:01 AM, James Nord wrote: > The code does not pass tests on windows. Using java8 you force me to use a > Virtual machine Can you be more specific about the problems you have? What tests do not pass? On Java 8 only you mean? If there are mistakes in

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I am -1000 on this. The code does not pass tests on windows. Using java8 you force me to use a Virtual machine which sucks. Using Windows subsystem for Linux gets you ubuntu 14.04 which does not have native support for JDK8. Basically please don't do this until you have a solution for

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

thanks Oliver 2016-12-01 9:08 GMT+01:00 ogondza : [...] > - Month 0: Announce the intention publicly, with this plan attached. > - Month 3: Drop support for Jenkins weekly. Declare what LTS will be the > last one to support the think we are dropping. Since we gave people

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Thu, Dec 1, 2016 at 3:08 AM, ogondza wrote: > is JDK 7 support really blocking us somewhere? Bugs > we cannot fix / need to awkwardly compensate, features we can not deliver on > Java 7? Of course not. It just slows down developers trying to work on new things in the name

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

The plan looks good to me. I'm also thinking about dropping the .NET 2.0 support in Windows installer and windows-slave-installer. If we drop Java 7, I would like to join the party and to announce the .NET2 and 3.5 deprecation and selection of .NET4 as a baseline. .NET 4 is 5 years old &&

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I am undecided on the subject. There clearly always are reasons to use newer/better version but is JDK 7 support really blocking us somewhere? Bugs we cannot fix / need to awkwardly compensate, features we can not deliver on Java 7? I felt much stronger against dropping Java 6 as we identified

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

> > >- As the next LTS/2.32 is already chosen, I guess the 2.32.1 should be >out early January (or late December?) > > Late December > >- Which means, the next baseline choice should happen around March or >April. > > It will be late February Hence, we could decide to switch to

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

FWIW, after the advice of Tyler, I created a blog entry on jenkins.io summarizing the numbers I posted previously: https://jenkins.io/blog /2016/11/22/what-jvm-versions-are-running-jenkins-the-return/ Seems like there's somehow an agreement, there's potentially some issues with the maven-plugin,

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Mon, Oct 31, 2016 at 10:22 AM, Arnaud Héritier wrote: > I really dislike this feature which is trying magically > to do a fix. I dislike it too, it is just a last resort for people who are too lazy to fix their project definitions to use Animal Sniffer, toolchains, etc.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I wasn't aware of this : https://jenkins.io/doc/upgrade-guide/ a big +1 On Mon, Oct 31, 2016 at 3:41 PM, Daniel Beck wrote: > > > On 31.10.2016, at 15:22, Arnaud Héritier wrote: > > > > It's up to the users to correctly read in details our release

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Yes we are agree but I really dislike this feature which is trying magically to do a fix. In the latest version of the plugin I tried to make visible the warning when it occurs. Building with with a JDK 8 and target/sources configured in java 7 is far from beeing perfect. But like I said I'm

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Sat, Oct 29, 2016 at 6:33 AM, Arnaud Héritier wrote: > The problem is that when a user have a large number of maven jobs running on > old JDKs, these are often legacy projects where the maintenance cost must be > 0. The problem is that using toolchains requires to update

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On 29/10/16 16:01, Arnaud Héritier wrote: Let's forget the maven job. Our statistics about its usage are useless as it was installed by default and we may hope that its usage is decreasing... AFAIK, basic usage of job types has always been available in the statistics. From the September CSV:

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

(replies inline) On Sat, 29 Oct 2016, Martina Riedel wrote: > It builds but it doesn't run. > From the README: go to the gameoflife-web directory and run mvn jetty:run. > The application will be running on http://localhost:9090. > > I don't see the Issues tab on >

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Hey, Please file an issue in the repo, or a PR. I was able to build the repo without an issue with Java 8, so this will need clarification... Thanks Le 29 oct. 2016 10:00 PM, "Martina" a écrit : My concern was that at some point jdk 7 will not be welcome in certain

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

There is an additional plugin which displays the version of the agent used (which is critical to manage too) https://wiki.jenkins-ci.org/display/JENKINS/VersionColumn+Plugin I would have loved to have this in info by default and I agree that the java version could make sense too On Sat, Oct 29,

RE: [DISCUSS] Time for Jenkins to require Java 8 to run

Any chance of getting a the manage nodes screen changed to include the java version for that agent, in advance of forcing Java 8 in the weekly builds? That would at least make it simpler for folks like myself to know the scale of the upcoming impact. Thanks, Kelly Hickel From:

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Let's forget the maven job. Our statistics about its usage are useless as it was installed by default and we may hope that its usage is decreasing... It remains that upgrading the java version of master is one thing. But you also need to upgrade the java version used by agents which aren't

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I think we should say "the first LTS of 2017 will require Java 8. End of conversation" That will mean that weekly releases should switch to Java 8 by mid-end November. 2017 it's a new year, it's a new Java version. We could look to solve some of the evil job type issues by *forking* remoting

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

2016-10-29 14:52 GMT+02:00 Arnaud Héritier : > From my POV the problem is that we don't know if we are talking about 5% > or 50% :( Well, since yesterday, we do know some things

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

>From my POV the problem is that we don't know if we are talking about 5% or 50% :( For sure, with any solution it will be painful for them. The risk being is that a big breakage for them gives the opportunity to move to something else. About communication/anticipation it is a mandatory

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Yes, but aren't we then back to the point, Arnaud: anyway, places/companies where cost must be 0 are not going to upgrade to new Jenkins version anyway? And when they're forced to upgrade at some point, in the meantime they're likely to have also been forced to upgrade the Jdk from 7 to 8 on

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

The problem is that when a user have a large number of maven jobs running on old JDKs, these are often legacy projects where the maintenance cost must be 0. The problem is that using toolchains requires to update you maven project and thus they'll probably won't do it :( Another solution may to

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I indeed think we will have to support the evil maven job type for one more decade, so need to make it flexible enough so migrating jenkins codebase to a newer JDK is not blocked y this beast. As maven do support toolchain, I just would like maven job do fully rely on it without any extra

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Are you proposing to write a real/good toolchain integration for Jenkins ? That will allow to generate / configure the config file based on what Jenkins deploys ? Ok with docker it is simpler to create an image with several JDKs and the configuration file hardcoded (in that case the challenge is

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

... or rely on tool chain, that has been designed to cover this exact issue. Didn't we had this debate few days ago ? Le 29 oct. 2016 9:48 AM, "Arnaud Héritier" a écrit : > If you don't use the maven evil job type > > Le samedi 29 octobre 2016, nicolas de loof

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

If you don't use the maven evil job type Le samedi 29 octobre 2016, nicolas de loof a écrit : > Jenkins can require Java 8, but needs to support building arbitrary Java > project, even jdk 1.0 ;) > > Le 29 oct. 2016 1:40 AM, "Martina"

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Jenkins can require Java 8, but needs to support building arbitrary Java project, even jdk 1.0 ;) Le 29 oct. 2016 1:40 AM, "Martina" a écrit : > btw. game-of-life that we all dearly love for demos only runs with jdk7, > not jdk 8, at least the master branch does.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

btw. game-of-life that we all dearly love for demos only runs with jdk7, not jdk 8, at least the master branch does. https://github.com/CloudBees-community/game-of-life Not sure how/where to report it, so I'm guessing that the right powers-to-be see this one. - Martina -- You received this

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Hello Folks, PR got merged, so now we have some data . I've twiddled with the raw json to make it more human readable, see that google spreadsheet

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Quick heads-up: we should have more data soon about the share of Java 8 & Java 7: https://github.com/jenkins-infra/infra-statistics/pull/21 In the meantime, any additional review/opinion on that change, and/or the data you think would be interesting to extract from there is welcome. 2016-10-19

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

One more thing https://issues.jenkins-ci.org/browse/JENKINS-37080 -- 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

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Have just read Java 9 is postponed to 2017/07/27, give us some extra time to look into this 2016-10-19 7:47 GMT+02:00 nicolas de loof : > @Oleg I totally agree we need to investigate java 9 support - for your > information, jenkins doesn't boot on java9+jigsaw, see >

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

@Oleg I totally agree we need to investigate java 9 support - for your information, jenkins doesn't boot on java9+jigsaw, see https://github.com/x-stream/xstream/issues/74 2016-10-18 23:42 GMT+02:00 Oleg Nenashev : > Weak -1 regarding JDK8, but the opinion is not that

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Weak -1 regarding JDK8, but the opinion is not that strong. I'm pretty sure that now it will be a pretty big problem for low-end platfroms like Embedded Systems with hand-made OpenJDK builds. We should rather consider investing into Java 9 Early Access IMHO. People will likely start submitting

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

ROR 2016-10-15 21:21 GMT+04:00 Arnaud Héritier : > FYI PR#66 I would like to apply Olivier's comment before applying it and > PR#66 daniel's comment. > > > Le samedi 15 octobre 2016, Arnaud Héritier a écrit : > >> I was supposed to work on it yesterday

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

FYI PR#66 I would like to apply Olivier's comment before applying it and PR#66 daniel's comment. Le samedi 15 octobre 2016, Arnaud Héritier a écrit : > I was supposed to work on it yesterday but I had a problem at home and I > had to stop to work early. There are 2 PRs I

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I was supposed to work on it yesterday but I had a problem at home and I had to stop to work early. There are 2 PRs I would like to finalize before the release. I hope to do it tomorrow evening or at the later on Monday. I don't know if Olivier had some others todo ? Le samedi 15 octobre 2016,

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I have no stacktrace and test case as we replaced guice to released version in our custom build. Will do of course when get again, but PR in core is blocked only by maven-plugin release. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Fri, Oct 14, 2016 at 3:10 AM, nicolas de loof wrote: > About maven job type, I wonder we could add better support for toolchain so > jenkins can aytomagically select/install adequate JDK on slave, create > toolchain.xml, and maybe even inject maven-toolchains-plugin

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I will jump for joy when everything is on Java 8. Functional features or death! Being able to consume the powerful libraries that are now Java 8-only (replacing Guava caches with Caffeine, for example, for a ~3x speed boost on all caching). Also @daniel-beck, this is another argument behind

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

FreeBSD : not sure how those handle packages vs system releases. http://www.freshports.org/java/openjdk8 doesn't give info on system version it applies to It's available at least in FreeBSD9.1 (which is already quite old) -- You received this message because you are subscribed to the

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

is there a jira issue to track this ? I've been running jenkins on Java 8 without issue so far, so wonder about this runtime issue. 2016-10-14 13:20 GMT+02:00 Kanstantsin Shautsou : > Jenkins still has guice-beta that randomly fails under java8. > > -- > You received

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Yes indeed, "OpenJDK 8 is included with RHEL 6.6 (and higher) and RHEL 7.1 (and higher), and it is fully supported." https://access.redhat.com/solutions/795263 java-package is available on jessie contrib

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Jenkins still has guice-beta that randomly fails under java8. -- 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.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Its a good move SUSE distributions which has OpenJDK 8: SLES 12 SP1 OpenSUSE 13.2 OpenSUSE Leap 42.1 fredag 14. oktober 2016 10.11.27 UTC+2 skrev Daniel Beck følgende: > > > > On 14.10.2016, at 09:10, nicolas de loof > wrote: > > > > About system that don't have Java 8

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

> On 14.10.2016, at 09:10, nicolas de loof wrote: > > About system that don't have Java 8 in official repo (RHEL5, Debian Wheezy, > Ubuntu 14.04 LTS). Are you saying that RHEL 6 + 7, Debian Jessie, and Ubuntu 16.04 all _do_ have JRE 8 in their repos? What about the

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

My +1 for Java 8 (as I have been advocating for this for 2.0 already) About system that don't have Java 8 in official repo (RHEL5, Debian Wheezy, Ubuntu 14.04 LTS). Oracle do provide official JDK builds as DEB/RPM, so I can't see this as a blocker. For sure there's IT department, one need to

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

> On 13.10.2016, at 22:22, Baptiste Mathus wrote: > >> On the wiki page of the plugin ? > > > Yes, I think this is probably the most sensible place. I agree. Can always be moved elsewhere if needed, but as it's plugin specific (and not even part of the default

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

2016-10-13 22:19 GMT+02:00 Arnaud Héritier : > > > On Thu, Oct 13, 2016 at 10:02 PM, Daniel Beck wrote: > >> >> > On 13.10.2016, at 20:36, Arnaud Héritier wrote: >> > >> > I just don't like to have such change in a minor release. >> >>

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Thu, Oct 13, 2016 at 10:08 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Just dont use the evil one > As soon as we'll provide a triggering mechanism like the evil job provides for SNAPSHOTs dependencies across projects it will be easy > > On 13 October 2016 at 21:02,

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Thu, Oct 13, 2016 at 10:02 PM, Daniel Beck wrote: > > > On 13.10.2016, at 20:36, Arnaud Héritier wrote: > > > > I just don't like to have such change in a minor release. > > We already did it in 1.612. > Yes and in 1.520 for Java 6. I tried to

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Just dont use the evil one On 13 October 2016 at 21:02, Daniel Beck wrote: > > > On 13.10.2016, at 20:36, Arnaud Héritier wrote: > > > > I just don't like to have such change in a minor release. > > We already did it in 1.612. > > The evil job type is a

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

> On 13.10.2016, at 20:36, Arnaud Héritier wrote: > > I just don't like to have such change in a minor release. We already did it in 1.612. The evil job type is a good point. Could Stephen or someone else who knows what they're talking about document how to circumvent

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Bye bye maven jobs that require java < 8 !!! I just don't like to have such change in a minor release. Otherwise +1 Le jeudi 13 octobre 2016, Baptiste Mathus a écrit : > Hey folks, > > As we've been discussing that again on IRC recently, we thought it might > be a good time to

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On Thu, Oct 13, 2016 at 12:13 PM, Manfred Moser wrote: > all developers are using 1.8 > and most testing is done 1.8 most likely as well. So from that background > any users should be running Jenkins 1.8 already. We might as well make it > official and drop 1.7 support.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

We recently did an upgrade to the latest 1.651.3 (latest 1.6 version) and had performance issues. When we switched to run it on Java 8 instead of Java 7 they all went away. We also had some plugin related problems. I am mentioning this because this shows that all developers are using 1.8 and most

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

> On 13.10.2016, at 17:53, R. Tyler Croy wrote: > > There's numbers in our usage data about which JREs are being used which needs > to get incorporated into stats.jenkins.io to help inform this discussion. Re-run what you did for

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

(replies inline) On Thu, 13 Oct 2016, Robert Sandell wrote: > I'm for it, > But didn't we discuss a new "deprecation policy" in the beginning of the > Jenkins 2 planning, or did I dream that? > I'm mostly thinking of the rollout of this, many installations seems to > have just dared to start

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Well, this thread is mostly IMO to see the trend/opinions to do it. We have not defined a timeline: we could probably for example issue a notice on the website that we'll do it on the first version of 2017, and then the next associated LTS after that date? That would still give a few more time

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I'm for it, But didn't we discuss a new "deprecation policy" in the beginning of the Jenkins 2 planning, or did I dream that? I'm mostly thinking of the rollout of this, many installations seems to have just dared to start thinking about upgrading to Jenkins 2, perhaps we shouldn't throw a Java

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Update already. Those in bizarre AIX, zOS and HPUX universes can continue to use older Jenkins versions. On Thu, Oct 13, 2016 at 1:29 PM, Baptiste Mathus wrote: > Hey folks, > > As we've been discussing that again on IRC recently, we thought it might > be a good time to

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Hi, According to http://www.oracle.com/technetwork/java/javase/ certconfig-2095354.html, Java 8 is supported for RHEL 5.5+ It is also available on IBM AIX and zOS, and on HP UX, where alternative JDKs do not exist: http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/welcome/

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

> On 13.10.2016, at 15:35, Stephen Connolly > wrote: > > Technically, at least on RHEL, OpenJDK 7 still has some legs > > https://access.redhat.com/articles/1299013 > > But then given that RHEL supports OpenJDK 6 until the end of this year and we > have

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

On 13 October 2016 at 13:29, Baptiste Mathus wrote: > Hey folks, > > As we've been discussing that again on IRC recently, we thought it might > be a good time to discuss that subject again. Latest thread about that I > could find is already 18+ months old >

[DISCUSS] Time for Jenkins to require Java 8 to run

Hey folks, As we've been discussing that again on IRC recently, we thought it might be a good time to discuss that subject again. Latest thread about that I could find is already 18+ months old