ci: configure actions/setup-java maven caching across workflows to fix 429 Too many requests flakiness - #14044
Open
lqiu96 wants to merge 1 commit into
Open
ci: configure actions/setup-java maven caching across workflows to fix 429 Too many requests flakiness#14044lqiu96 wants to merge 1 commit into
Too many requests flakiness#14044lqiu96 wants to merge 1 commit into
Conversation
…x 429 flakiness Enable 'cache: maven' in 'actions/setup-java' across 27 GitHub Actions workflows to eliminate redundant dependency downloads and mitigate HTTP 429 (Too Many Requests) rate limiting errors from Maven Central. Remove fragile and deprecated week-of-year date steps and custom actions/cache configs that conflicted with native setup-java caching. Error logs observed prior to fix: ``` 18:31:58:640 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.6.0:check (checkstyle) on project gax-bom: Execution checkstyle of goal org.apache.maven.plugins:maven-checkstyle-plugin:3.6.0:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:3.6.0 or one of its dependencies could not be resolved: 18:31:58:640 [ERROR] Failed to read artifact descriptor for org.iq80.snappy:snappy:jar:0.4 ... 18:33:16:682 [ERROR] The project com.google.api:gax-bom:2.84.0-SNAPSHOT (/home/runner/work/google-cloud-java/google-cloud-java/sdk-platform-java/gax-java/gax-bom/pom.xml) has 1 error 18:33:16:682 [ERROR] Non-resolvable parent POM for com.google.api:gax-bom:2.84.0-SNAPSHOT: The following artifacts could not be resolved: com.google.cloud:google-cloud-shared-config:pom:1.17.0 (absent): com.google.cloud:google-cloud-shared-config:pom:1.17.0 failed to transfer from https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact com.google.cloud:google-cloud-shared-config:pom:1.17.0 from/to central (https://repo.maven.apache.org/maven2): status code: 429, reason phrase: Too Many Requests (429) and 'parent.relativePath' points at no local POM @ line 11, column 11 -> [Help 2] ```
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
|
lqiu96
marked this pull request as ready for review
August 11, 2026 19:38
lqiu96
enabled auto-merge (squash)
August 11, 2026 19:38
jinseopkim0
approved these changes
Aug 11, 2026
Too many requests flakiness
Too many requests flakinessToo many requests flakiness
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.



Enable 'cache: maven' in 'actions/setup-java' across the remaining GitHub Actions workflows to eliminate redundant dependency downloads and mitigate HTTP 429 (Too Many Requests) rate limiting errors from Maven Central.
There may be a better/ bigger long-term fix for this. But adding some caching for CIs should help resolve a lot of these flaky 429 issues causing the CIs to fail randomly.
Additionally, remove fragile and deprecated week-of-year date steps and custom actions/cache configs that conflicted with native setup-java caching.
Error logs:
From: https://github.com/googleapis/google-cloud-java/actions/runs/31522962200/job/93884821458?pr=14029