Repository navigation
ci: retry the Gradle resolve instead of failing on one 404 - #513
Merged
Merged
Conversation
A cold Gradle cache has to fetch every plugin from Maven Central and the Plugin Portal, and a single 404 there fails the build before a line of Kotlin compiles. PR #512 failed twice that way in 35 s on artifacts that resolve fine from every other network — including a decade-old `annotations:13.0` — and so did #508, while the PRs around them built in four minutes. The build now retries up to three times, clearing the module cache between attempts so a half-written resolve cannot poison the next one. Same for the Develop build, which shares the failure mode.
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.
What changed
The PR and Develop builds retry the Gradle resolve up to three times, clearing the module cache between attempts, instead of failing on the first 404.
Why
PR #512 failed twice in ~35 s with:
That is plugin resolution, before any code compiles. Every one of those artifacts answers 200 from here - including annotations:13.0, which is a decade old - and the runs around it (#166, #167, #168) built in four minutes on the same runners. #165 (PR #508) failed the same way. So it is a transient registry failure on a cold cache, not a broken dependency.
Testing
The red run on #512 stays red, because a re-run uses the workflow pinned to that commit. That is why this lands on its own.