Skip to content

ci: configure actions/setup-java maven caching across workflows to fix 429 Too many requests flakiness - #14044

Merged
lqiu96 merged 2 commits into
mainfrom
fix_ci_maven_flakiness
Aug 12, 2026
Merged

ci: configure actions/setup-java maven caching across workflows to fix 429 Too many requests flakiness#14044
lqiu96 merged 2 commits into
mainfrom
fix_ci_maven_flakiness

Conversation

@lqiu96

@lqiu96 lqiu96 commented Aug 11, 2026

Copy link
Copy Markdown
Member

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:

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]

From: https://github.com/googleapis/google-cloud-java/actions/runs/31522962200/job/93884821458?pr=14029

…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]
```
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@lqiu96
lqiu96 marked this pull request as ready for review August 11, 2026 19:38
@lqiu96
lqiu96 requested review from a team as code owners August 11, 2026 19:38
@lqiu96
lqiu96 requested a review from jinseopkim0 August 11, 2026 19:38
@lqiu96
lqiu96 enabled auto-merge (squash) August 11, 2026 19:38
@lqiu96 lqiu96 changed the title ci: configure actions/setup-java maven caching across workflows to fix 429 flakiness ci: configure actions/setup-java maven caching across workflows to fix 429 Too many requests flakiness Aug 11, 2026
@lqiu96 lqiu96 changed the title ci: configure actions/setup-java maven caching across workflows to fix 429 Too many requests flakiness ci: configure actions/setup-java maven caching across workflows to fix 429 Too many requests flakiness Aug 11, 2026
@sonarqubecloud

Copy link
Copy Markdown

@sonarqubecloud

Copy link
Copy Markdown

Comment thread .github/workflows/ci.yaml
with:
distribution: temurin
java-version: ${{matrix.java}}
cache: maven

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be cautious of introducing cache in general. We've seen cache caused other issues such as not using the latest versions before.
How often do we see this issue? Is this issue caused by unstable Maven central?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed offline that this may cause false positive CIs that code changes in Gax/Auth are not propagated to downstream tests.

@lqiu96
lqiu96 merged commit 0bcc963 into main Aug 12, 2026
229 checks passed
@lqiu96
lqiu96 deleted the fix_ci_maven_flakiness branch August 12, 2026 06:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants