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

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

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

>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

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

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

(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: @DataBoundConstructor with object in constructor

Okey dokie, I think I'm nearly out of the woods. I can now create a pipeline job. Unfortunately, I also have a problem with a descriptor constructor. With this new code, we are now seeing errors calling the new subclass descripters. This output is shown in:

Re: builds verification for stapler/stapler

I was incorrect earlier in my request for permissions for my account (rtyler) to the stapler organization. Apparently writers to the org cannot invite folks to new teams. Anyways, my preference would be to be granted Admin for the stapler org. Failing that, somebody needs to invite the

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

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

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

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

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

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