Repository navigation
Validate the Gradle wrapper with setup-gradle - #123
Merged
Merged
Conversation
The separate gradle/wrapper-validation-action@v3 downloaded the checksums of all Gradle versions from services.gradle.org on every run and timed out regularly. setup-gradle@v6 validates the wrapper by default, so the step is dropped.
Qodana for JVMIt seems all right 👌 No new problems were found according to the checks applied View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2026.2.2
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
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
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.
The Build job failed repeatedly at "Gradle Wrapper Validation" with a request timeout: the old
gradle/wrapper-validation-action@v3(internally gradle/actions v3.5.0) does not know the checksums of newer wrappers and downloads them for every Gradle version from services.gradle.org on each run.gradle/actions/setup-gradle@v6, which every job already uses, validates all wrapper jars by default (validate-wrappers: true), so the separate step is removed instead of being upgraded.No changelog entry, CI only.