Need guide to upgrade Java 1.8 to 17

Using Jenkins
1

Hello Team,
We will be upgrading our Jenkins from 2.346.2 to 2.426.3 .
Since I got the information from community to upgrade Java to Temurin JDK, [17.0.11+9] is it also recommended to install the same java version across all the agents as well ?

If yes can you help me with Java upgrade guide from openJDK 1.8 to Temurin 17.0.11+9

Some machine details:

openjdk version “1.8.0_332”
OpenJDK Runtime Environment (build 1.8.0_332-8u332-ga-1~deb9u1-b09)
OpenJDK 64-Bit Server VM (build 25.332-b09, mixed mode)

PRETTY_NAME=“Debian GNU/Linux 9 (stretch)”

NAME=“Debian GNU/Linux”

VERSION_ID=“9”

VERSION=“9 (stretch)”

VERSION_CODENAME=stretch

ID=debian

HOME_URL=“https://www.debian.org/”

SUPPORT_URL=“Debian -- User Support”

BUG_REPORT_URL=“https://bugs.debian.org/”

2

You should upgrade your whole setup!

Security updates have been discontinued for Debian Stretch as of July 6th, 2020!!!

It also does not make sense to use Java 17 anymore, use the latest LTS 21.
Your agents can run any Java version that you need.

1 Like
3

@uhafner Thanks for your reply. Any specific version and flavour of Java can you help us to point

Also we are using Docker : Docker version 19.03.15, build 99e3ed8919
Do we need to upgrade Docker to any specific version

4

As per this post we planned to : Upgrade Guide for Jenkins LTS 2.426.3 - #7 by poddingue

upgrade java to Temurin JDK, so 17.0.11+9 will it not be recommended ?

So , agents still can run JDK 1.8 and Jenkins controller can be upgraded to JAVA 17/21 ?

Our Current Agent Config:

Manifest-Version: 1.0

Application-Name: Jenkins Remoting Agent

Permissions: all-permissions

Codebase: *

Trusted-Library: true

Build-Jdk-Spec: 1.8

Version: 4.13.2

Created-By: Maven JAR Plugin 3.2.2

Main-Class: hudson.remoting.Launcher

1 Like
5

Agents should be launched with the same Java version as is used on the controller.

You are using a very old version of the agent. It appears that you are using an inbound agent, starting the agent from the agent computer. If you continue using that type of agent, then you should upgrade the agent.jar file to the version that is included with the upgraded Jenkins controller.

Agents can run jobs and perform builds with any Java version that you prefer. The Jenkins “tools” system allows a job to choose the specific version of Java that should run the job.

A stack overflow article provides more details for job configuration of specific Java versions. There is also a video from Darin Pope:

2 Likes
6

I agree with Ulli’s comment and have one more reason to offer for the upgrade. Jenkins 2.452.1 won’t run the Debian installer on Debian Stretch or earlier. The Jenkins installer for Debian now requires apt that is Debian 10 or newer. Refer to packaging issue 455 and packaging pull request 456 for more details.

2 Likes