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
| Assignee | Original: Baptiste Mathus [ batmat ] | New: Adrien Lecharpentier [ alecharp ] |
| Link |
New:
This issue is blocked by |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Assignee | Original: Adrien Lecharpentier [ alecharp ] | New: Baptiste Mathus [ batmat ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |