ci: stop using Google's Maven mirror in downstream checks#12826
Merged
suztomo merged 1 commit intogoogleapis:mainfrom Apr 16, 2026
Merged
ci: stop using Google's Maven mirror in downstream checks#12826suztomo merged 1 commit intogoogleapis:mainfrom
suztomo merged 1 commit intogoogleapis:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the .kokoro/downstream-compatibility.sh script by removing the setup_maven_mirror call and adding a git diff output to display dependency modifications during testing. The review feedback suggests using git --no-pager diff to ensure the CI environment does not hang due to an interactive pager.
| update_all_poms_dependency "$repo" google-cloud-shared-dependencies "$SHARED_DEPS_VERSION" | ||
| pushd "$repo" | ||
| echo "Diff to run the test with modified dependencies:" | ||
| git diff |
Contributor
There was a problem hiding this comment.
In CI environments, it is a best practice to use git --no-pager diff to ensure the command never attempts to open an interactive pager, which could cause the build to hang indefinitely if the environment is not correctly configured for non-interactive use.
Suggested change
| git diff | |
| git --no-pager diff |
Member
Author
chingor13
approved these changes
Apr 16, 2026
Neenu1995
pushed a commit
that referenced
this pull request
Apr 17, 2026
For #12824. The use of the Maven Central mirror is the causes of the failures: `Error: Non-resolvable parent POM for com.google.cloud:google-cloud-bigtable-parent:2.77.1: The following artifacts could not be resolved: com.google.cloud:sdk-platform-java-config:pom:3.59.0 (absent): com.google.cloud:sdk-platform-java-config:pom:3.59.0 was not found in https://maven-central.storage-download.googleapis.com/maven2/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of google-maven-central has elapsed or updates are forced and 'parent.relativePath' points at no local POM @ line 14, column 13 -> [Help 2]` b/31927595#comment86 for the cause.
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.

For #12824. The use of the Maven Central mirror is the causes of the failures:
Error: Non-resolvable parent POM for com.google.cloud:google-cloud-bigtable-parent:2.77.1: The following artifacts could not be resolved: com.google.cloud:sdk-platform-java-config:pom:3.59.0 (absent): com.google.cloud:sdk-platform-java-config:pom:3.59.0 was not found in https://maven-central.storage-download.googleapis.com/maven2/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of google-maven-central has elapsed or updates are forced and 'parent.relativePath' points at no local POM @ line 14, column 13 -> [Help 2]b/31927595#comment86 for the cause.