CI: Bump 'JVM Tests - JDK 15' to JDK 16 and EA job to 17-ea #17082
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
and bump 'Early Access JDK Build' to JDK 17-ea Resolves #16195
quarkus-bot
bot
added
the
area/infra-automation
|
Btw, it's a bit ironic that the EA job is testing more areas with latest GA JDK than the regular CI. Maybe we should introduce a weekly devtools/maven/gradle/tcks job with JDK 16? 🤔 |
gsmet
approved these changes
May 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
and bump 'Early Access JDK Build' to JDK 17-ea
Resolves #16195
The EA job will fail with many probelms. I had a quick look and e.g. mockito is not yet compatible with Java 17 (ASM that is).
But that's not a pressing problem ATM.