Critical The Jenkins Project has started digging more deeply into what is needed to make Jenkins work on JDK11.
We should see what it takes to make Evergreen work on JDK11 too. It makes much sense because contrary to the usual Jenkins distro, we can easily specific specific plugin versions, where for instance there's only incremental releases but not common-maven type releases.
We most probably want to implement this using a new flavor, like docker-cloud-jdk11 for instance so that we can actually even deploy in production and test it in a normal way without disturbing the other existing flavors. If this proves successful, we can then see how/if we want to propage this to the existing docker-cloud and/or aws-ec2-cloud flavors.
Acceptance criteria:
- A docker-cloud on JDK 11 flavor available for testing using the usual way of starting an Evergreen instance (but using a different Docker image tag) (https://jenkins.io/projects/evergreen/)
- is blocked by
-
JENKINS-54292 Align/fix the codebase to use flavor everywhere instead of environment
-
- Resolved
-
[JENKINS-54598] Explore JDK11 Upgrade for Evergreen
Adrien Lecharpentier
added a comment - At this moment, evergreen base image is based on alpine. This "distribution" has no support yet for JDK 11, it seems not feasible to have this port. I tried to use adoptopenjdk but it's not helping easier. They have a Dockerfile for JDK11 on alpine [1], but it's not possible to use it to build an image with JDK 11.
At this time, I'm not confident we can have a jdk 11 on the evergreen base image. We would need to rethink the entire packaging mechanism.
Adrien Lecharpentier
added a comment - At this moment, evergreen base image is based on alpine . This "distribution" has no support yet for JDK 11, it seems not feasible to have this port. I tried to use adoptopenjdk but it's not helping easier. They have a Dockerfile for JDK11 on alpine [1] , but it's not possible to use it to build an image with JDK 11.
At this time, I'm not confident we can have a jdk 11 on the evergreen base image. We would need to rethink the entire packaging mechanism.
[1] https://raw.githubusercontent.com/AdoptOpenJDK/openjdk-docker/master/11/jdk/alpine/Dockerfile.openj9.releases.full This is now fixed.
One can test this using the steps described in the official documentation https://jenkins.io/projects/evergreen/, but using the java11-docker-cloud Docker tag instead.
I.e.
docker volume create jenkins-evergreen-data && \
docker pull jenkins/evergreen:java11-docker-cloud && \
docker run --name evergreen \
--restart=always \
-ti \
-p 8080:80 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v jenkins-evergreen-data:/evergreen/data \
-e LOG_LEVEL=info \
jenkins/evergreen:java11-docker-cloud
Going to tackle
JENKINS-54292in expedite. Though not technically blocking, it's small enough that it should be done quickly before more people start losing time understanding this "environment" thing.