Run Gradle release candidate tests with JDK 17#690
Merged
Conversation
Contributor
Job Summary for GradleDemo adding Build Scan® comment to PR :: successful-build-with-always-comment
|
This was referenced Jul 24, 2025
clayburn
approved these changes
Jul 28, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue
Since Gradle 9, JDK 17 is the minimal version to run Gradle (ref)
Some of the GH workflows in this repository are failing (example) when running against the release candidate (being Gradle 9)
Fix
Create a dedicated provision-gradle job with JDK 17 instead of the default 11.
This change is a minimalistic way to fix the issue.