-
Task
-
Resolution: Fixed
-
Minor
In https://github.com/jenkinsci/docker/pull/690/commits/ffe36e0f9d6d94b1c10e2fc71751e5fbba0a26f4 and https://github.com/jenkinsci/docker/pull/690 only base images have been adjusted to Java 10 and 11 (in java10 and java11 branches). We need to upstream these changes and integrate into the common weekly release flow.
It would be also great to update Alpine and Slim images as well so that they can be shipped within the common release flow (if possible & feasible).
Attack plan 1: additional Dockerfile in the repo
- Take https://github.com/jenkinsci/docker/blob/java11/Dockerfile and put it to master (Dockerfile-jdk11)
- Update scripts to also build and publish Java 11
- Risk: The build runs on Trusted CI, may need help from olblak . May have issues with debugging
- Possible resolution: parameterize scripts and deploy to jenkins4eval (for local debugging). oleg_nenashev can help with permissions
Attack plan 2: via multi-platform
- Get https://github.com/jenkinsci/docker/pull/719 integrated
- Upstream Java 11 support patches from https://github.com/jenkinsci/remoting/pull/292 to the master scripts
- Enable the new build mode on trusted-ci which can deploy images
- links to
[JENKINS-51985] Create official jenkins/jenkins Docker images for Java 11
Recommendation from the OpenJDK Jigsaw Leads is to avoid using there OpenJDK images and to build our own images
Do you mean a custom runtime image built with jlink?
Nope, just building the images from scratch and downloading OpenJDK from official resources.
> Do you mean a custom runtime image built with jlink?
We should carefully use it for the master, because we do not know what may be required by plugins
So, if somebody decides to build it, the entire JVM should be included as well as some modules
duemir I have adjusted the ticket description a bit to reflect the current status and the needs for the Weekly release. Sorry if I am hijacking the ticket a bit, can create another one.
oleg_nenashev No worries. I can still try and have a crack at it or just drop back to Unassigned.
The proposal is to go with the option 1 right now, because it saves a lot of time
First pre-stab https://github.com/jenkinsci/docker/pull/760 in review.
batmat sorry for the late check. The tag naming patter for the released "latest" versions differ from what is defined in JEP-211: https://github.com/jenkinsci/jep/tree/master/jep/211#jenkins-master-images-jenkins-51985 . We either need to change JEP or to fix the PR
The core scope/goal of this is done. But an /infra/ bug was detected and and is being fixed in JENKINS-54725
yes, there are no alpine images so has to go without them