Jenkins requires Java 11 since June 2022 for the weekly release line and September 2022 for LTS release line.
For the jenkinsci/docker-agent and jenkinsci/docker-inbound-agent, a last release had been delivered a few month ago with the latest remoting agent.jar compatible with JDK8 (ref. https://github.com/jenkinsci/docker-agent/issues/298).
For the SSH agent image here, there is no requirement around the agent.jar because it is not part of the image.
However it does not make sense to ship JDK8 version anymore.
Proposal: we should deprecate JDK8 SSH agent images (and associated tooling such as dependabot) in a new 5.x.y release line (current release is 4.10.0) on the principal branch.
The only "danger" is to be careful to properly write the changelog (either with good PR title and labelling to hint release-drafter, or even when publishing the release).
Ping @poddingue @MarkEWaite @timja @NotMyFault @basil @halkeye @jglick @imonteroperez do you see any potential problem for this?
Jenkins requires Java 11 since June 2022 for the weekly release line and September 2022 for LTS release line.
For the jenkinsci/docker-agent and jenkinsci/docker-inbound-agent, a last release had been delivered a few month ago with the latest remoting
agent.jar
compatible with JDK8 (ref. https://github.com/jenkinsci/docker-agent/issues/298).For the SSH agent image here, there is no requirement around the
agent.jar
because it is not part of the image. However it does not make sense to ship JDK8 version anymore.Proposal: we should deprecate JDK8 SSH agent images (and associated tooling such as dependabot) in a new
5.x.y
release line (current release is4.10.0
) on the principal branch.The only "danger" is to be careful to properly write the changelog (either with good PR title and labelling to hint release-drafter, or even when publishing the release).
Ping @poddingue @MarkEWaite @timja @NotMyFault @basil @halkeye @jglick @imonteroperez do you see any potential problem for this?