Re: Using JDK 11 instead of JDK 8 in default docker images

Thank you for your answer, Jesse. I do not consider the solution of cross-compiling or running commands on a Linux agent and then commands over SSH as being useful. While I cannot speak for the community, this would remove any advantage to having Jenkins involved and I suspect that a

Re: Using JDK 11 instead of JDK 8 in default docker images

Due to the way Jenkins performs remote class loading and allows plugins to implement callables, is is impractical to support Java 8 on agents without forcing Jenkins core and all commonly used plugins to run on 8 as well. At worst, builds on exotic OSs with poor Java support can still be done by

RE: Using JDK 11 instead of JDK 8 in default docker images

if the above question were asked in the design phase. That’s just my $.02US, for what it’s worth. Bill From: jenkinsci-dev@googlegroups.com On Behalf Of Tim Jacomb Sent: Wednesday, August 11, 2021 2:46 PM To: jenkinsci-dev@googlegroups.com Subject: Re: Using JDK 11 instead of JDK 8

Re: Using JDK 11 instead of JDK 8 in default docker images

Jetty, Hikari, and opensaml are all projects I’ve come across recently where new development has a minimum Java 11 version… there’s probably many others On Wed, 11 Aug 2021 at 16:03, Matt Sicker wrote: > Plus Java 17 comes out really soon. I can imagine that will inspire more > projects to set

RE: Using JDK 11 instead of JDK 8 in default docker images

, etc.). Bill -Original Message- From: jenkinsci-dev@googlegroups.com On Behalf Of Matt Sicker Sent: Wednesday, August 11, 2021 12:37 PM To: jenkinsci-dev@googlegroups.com Subject: Re: Using JDK 11 instead of JDK 8 in default docker images I mean there's a very real chance

Re: Using JDK 11 instead of JDK 8 in default docker images

rms where the story is similar but am not an expert > on them. > > > > > > From: jenkinsci-dev@googlegroups.com On > Behalf Of Matt Sicker > Sent: Wednesday, August 11, 2021 10:03 AM > To: jenkinsci-dev@googlegroups.com > Subject: Re: Using JDK 11 instead of JDK 8 in de

RE: Using JDK 11 instead of JDK 8 in default docker images

: Using JDK 11 instead of JDK 8 in default docker images Plus Java 17 comes out really soon. I can imagine that will inspire more projects to set Java 11 as a baseline. Definitely start planning since most people will probably be affected by some other dependencies well before they hit Jenkins

Re: Using JDK 11 instead of JDK 8 in default docker images

Plus Java 17 comes out really soon. I can imagine that will inspire more projects to set Java 11 as a baseline. Definitely start planning since most people will probably be affected by some other dependencies well before they hit Jenkins. Matt Sicker > On Aug 11, 2021, at 09:18,

Re: Using JDK 11 instead of JDK 8 in default docker images

Hi Bill (et al) for those that are running nonstop or the like and have an update / test cycle in the order of 6 months : I would recommend that your customers probably want to start the planning / validation to update to Java11 now even if this LTS version still runs on Java8. Java11 is

Re: Using JDK 11 instead of JDK 8 in default docker images

Mark, Randall had pointed me to this thread. I admit to only reading the last couple of dozen posts and, based only on that, share my concerns. I should have spent more time reading the thread, but I was scheduled to do a code walkthrough with my customer and took the 'short' path, for which

Re: Using JDK 11 instead of JDK 8 in default docker images

Thanks for sharing your insights. Great to have participation in the thread. Comments are inline On Wednesday, August 4, 2021 at 2:39:05 PM UTC-6 bhon wrote: > Similar to Randall (the.n...), I have customers that use NonStop, but they > also use various distros of Enterprise Linux. Their

Re: Using JDK 11 instead of JDK 8 in default docker images

I am incredibly relieved!!! Thanks Mark, for the clarification. This would have been a sleep-loss situation. I have to hold things together until at least December 2023, on this topic. On Wednesday, August 4, 2021 at 4:37:35 p.m. UTC-4 Mark Waite wrote: > On Wed, Aug 4, 2021 at 1:11 PM

Re: Using JDK 11 instead of JDK 8 in default docker images

Similar to Randall (the.n...), I have customers that use NonStop, but they also use various distros of Enterprise Linux. Their corporate strategy for software development is to remain on Java 8 for the foreseeable future, primarily due to the JDK 11 licensing mentioned above. They have a

Re: Using JDK 11 instead of JDK 8 in default docker images

On Wed, Aug 4, 2021 at 1:11 PM the.n...@gmail.com wrote: > That's assuming that Docker runs on NonStop, which it doesn't. The key > issue is remoting.jar and whether that can be maintained at 1.8 > compatibility. Most groups are using a Controller/Agent architecture using > Docker for the

Re: Using JDK 11 instead of JDK 8 in default docker images

That's assuming that Docker runs on NonStop, which it doesn't. The key issue is remoting.jar and whether that can be maintained at 1.8 compatibility. Most groups are using a Controller/Agent architecture using Docker for the Controller and running the platform JVM for remoting.jar. There are a

Re: Using JDK 11 instead of JDK 8 in default docker images

On Wed, Aug 4, 2021 at 2:13 PM Randall Becker wrote: > when deploying Jenkins into production environments […] using the Oracle > JRE is a requirement not an option > If your environment has specialized needs, including legal ones, you can of course build your own Docker images accordingly

RE: Using JDK 11 instead of JDK 8 in default docker images

instead of JDK 8 in default docker images We aren't using Oracle's JDK in the images, we are using the Adoptium project's JDK.  On Wed, Aug 4, 2021 at 11:04 AM the.n...@gmail.com <the.n.e@gmail.com> wrote:I'm sorry I missed this meeting - other obligations. We are stuck on JDK 8 for a v

Re: Using JDK 11 instead of JDK 8 in default docker images

We aren't using Oracle's JDK in the images, we are using the Adoptium project's JDK. On Wed, Aug 4, 2021 at 11:04 AM the.n...@gmail.com wrote: > I'm sorry I missed this meeting - other obligations. We are stuck on JDK 8 > for a variety of reasons, including Oracle's JDK 11 license terms, which

Re: Using JDK 11 instead of JDK 8 in default docker images

I'm sorry I missed this meeting - other obligations. We are stuck on JDK 8 for a variety of reasons, including Oracle's JDK 11 license terms, which are significantly different from JDK 8, and also that JDK 11 is not available on our ia64 platform. How long will JDK 8 builds continue to be

Re: Using JDK 11 instead of JDK 8 in default docker images

I've submitted the Jenkins Enhancement Proposal that proposes to switch from JDK 8 to JDK 11 for the Jenkins 2.302.1 LTS release on Aug 25, 2021. Pull request is https://github.com/jenkinsci/jep/pull/374/files File content view is:

Re: Using JDK 11 instead of JDK 8 in default docker images

I believe that the plan from the Contributor Summit aligns with Oleg's vote that he cast in advance. The Platform SIG will meet today and has Java 11 on the agenda for further discussion. Contributor summit notes are recorded in a Google Doc

Re: Using JDK 11 instead of JDK 8 in default docker images

Hi all, Looking forward to see the discussion from the contributor summit summarized here. Sadly I missed it due to having another session, but I've heard it was a great discussion that resulted in a proposal. Thanks to Mike Cirioli and Mark Waite for driving this topic at the summit, and

Re: Using JDK 11 instead of JDK 8 in default docker images

Allow me to append myself to the list of developers who would like access to Java 11 APIs. If we had access to Java 11 APIs, then this

Re: Using JDK 11 instead of JDK 8 in default docker images

I'm more conservative with my concept for the September plan. I think we should change the base images to Java 11 but don't need to make any decision related to Java 8. We'll discuss further in the Platform SIG meeting today On Thursday, June 17, 2021 at 9:58:21 AM UTC-6 Michael Cirioli

Re: Using JDK 11 instead of JDK 8 in default docker images

Adding my $.02 I am in support of making java11, and would like to help move this forward. It is great that there is now an admin monitor which should help raise awareness (and appetite) , but what other actionable items need to happen? - communicate plan to address remaining java11

Re: Using JDK 11 instead of JDK 8 in default docker images

The docs on Jenkins.Io, dockerhub and in the docker GitHub repo were all updated to use the jdk11 variant but the latest image tag isn’t changed yet On Mon, 14 Jun 2021 at 15:03, Slide wrote: > I think Mark was looking at doing the migration in September if I remember > correctly. > > On Mon,

Re: Using JDK 11 instead of JDK 8 in default docker images

I think Mark was looking at doing the migration in September if I remember correctly. On Mon, Jun 14, 2021 at 6:20 AM 'Olblak' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > What the current state here? > Looks like the docker image still use java 8 by default but the helm

Re: Using JDK 11 instead of JDK 8 in default docker images

What the current state here? Looks like the docker image still use java 8 by default but the helm chart switched to java 11 Should we talk about switching to java11 by default during the contributor summit? On Monday, 10 May 2021 at 15:47:41 UTC+2 timja...@gmail.com wrote: > What metric would

Re: Using JDK 11 instead of JDK 8 in default docker images

What metric would people consider? 0? Few new issues? From personal experience on Java 11 I have never hit the above issues (apart from illegal reflective access log messages) Query I used to look:

Re: Using JDK 11 instead of JDK 8 in default docker images

On Sun, May 9, 2021 at 4:10 AM Tim Jacomb wrote: > encourage existing users to migrate > Feels a bit premature when the list of `java11-compatibility` issues still includes bugs in core and widely used plugins. (The only ones I have personal experience with are JENKINS-61212

Re: Using JDK 11 instead of JDK 8 in default docker images

Lemme review it tonight. It would be nice to explicitly list compat issues like JAXB, though we could rather go ahead and fix the plugins instead. If we could get plugin EOL JEP from Basil accepted, that would be quite easy to do On Sun, May 9, 2021, 11:23 Tim Jacomb wrote: > Anything

Re: Using JDK 11 instead of JDK 8 in default docker images

Anything specifically need refreshing there? The upgrade step could possibly be removed as java 11 has been supported for a long time at this point On Sun, 9 May 2021 at 09:49, Oleg Nenashev wrote: > Before we communicate anything to users, I think we should refresh >

Re: Using JDK 11 instead of JDK 8 in default docker images

FTR here is the query for known Java 11 compatibility issues in Jira. Some issues are not a blocker, for example Illegal Reflective Access which will become a big

Re: Using JDK 11 instead of JDK 8 in default docker images

Hi, I am definitely in favor of switching to jdk11 by default, it's really time to move forward. We have been using it on the Jenkins infrastructure project for almost a year now without major issues but we also had to fine-tune the java configuration for java 11. That remains a major change

Re: Using JDK 11 instead of JDK 8 in default docker images

Defaults and (people not seeing a need to change) Shipping an ‘admin monitor’ encouraging people to update would probably make a difference On Wed, 28 Apr 2021 at 17:18, Tim Jacomb wrote: > It’s just down to defaults I think. > > We’ve seen the numbers rise as we changed the website and helm

Re: Using JDK 11 instead of JDK 8 in default docker images

It’s just down to defaults I think. We’ve seen the numbers rise as we changed the website and helm chart to use Java 11 by default On Wed, 28 Apr 2021 at 17:08, Daniel Beck wrote: > > > On Wed, Apr 28, 2021 at 1:42 AM Oleg Nenashev > wrote: > >> I am in favor of making JDK11 the default in

Re: Using JDK 11 instead of JDK 8 in default docker images

On Wed, Apr 28, 2021 at 1:42 AM Oleg Nenashev wrote: > I am in favor of making JDK11 the default in all our distributions, > including controller and agent Docker images. > At the same time I am afraid that removal of Java 1.8 support is > premature. The vast majority of Jenkins users still uses

Re: Using JDK 11 instead of JDK 8 in default docker images

A transition period using Java 11 Docker images with Java 8 compatibility would be useful IMO. On Tue, 27 Apr 2021 at 22:21, Raihaan Shouhell wrote: > > Perhaps removal of java 8 support should come with a bump in major version > number so jenkins 3.x and an announcement ahead of time. > >

Re: Using JDK 11 instead of JDK 8 in default docker images

Perhaps removal of java 8 support should come with a bump in major version number so jenkins 3.x and an announcement ahead of time. Cheers, Raihaan On Wed, Apr 28, 2021, 7:42 AM Oleg Nenashev wrote: > I am in favor of making JDK11 the default in all our distributions, > including controller

Re: Using JDK 11 instead of JDK 8 in default docker images

I am in favor of making JDK11 the default in all our distributions, including controller and agent Docker images. At the same time I am afraid that removal of Java 1.8 support is premature. The vast majority of Jenkins users still uses this version, and the migration to Java 11 won't be

Re: Using JDK 11 instead of JDK 8 in default docker images

I agree with dropping java 8. There are some nice features in 11 that would be good to use. On Tue, Apr 27, 2021 at 9:11 AM Tim Jacomb wrote: > We’ve been using it for over a year on java 11 and never hit an issue... > > I would rather drop java 8 as well > > On Tue, 27 Apr 2021 at 15:48, Jesse

Re: Using JDK 11 instead of JDK 8 in default docker images

We’ve been using it for over a year on java 11 and never hit an issue... I would rather drop java 8 as well On Tue, 27 Apr 2021 at 15:48, Jesse Glick wrote: > My opinion remains that if we believe Java 11 support is solid enough to > be the default, then we may as well keep things simple and

Re: Using JDK 11 instead of JDK 8 in default docker images

My opinion remains that if we believe Java 11 support is solid enough to be the default, then we may as well keep things simple and drop Java 8 support: start building core and important plugins with `java.level=11`, and take advantage of its features. Building and testing primarily against 8

Using JDK 11 instead of JDK 8 in default docker images

The Jenkins docker images are currently using Java 8 unless the image name specifically includes 'jdk11' in the name. The platform SIG discussed last Friday that we think September 2021 would be a good goal to deliver JDK 11 as the standard JDK in those images instead of JDK 8. This change