Skip to content

ci: stop using Google's Maven mirror in downstream checks#12826

Merged
suztomo merged 1 commit intogoogleapis:mainfrom
suztomo:main
Apr 16, 2026
Merged

ci: stop using Google's Maven mirror in downstream checks#12826
suztomo merged 1 commit intogoogleapis:mainfrom
suztomo:main

Conversation

@suztomo
Copy link
Copy Markdown
Member

@suztomo suztomo commented Apr 16, 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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

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.

Comment thread .kokoro/downstream-compatibility.sh Outdated
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
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.

medium

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

@suztomo
Copy link
Copy Markdown
Member Author

suztomo commented Apr 16, 2026

The downstream checks passed:

image

@suztomo suztomo marked this pull request as ready for review April 16, 2026 23:01
@suztomo suztomo requested a review from a team as a code owner April 16, 2026 23:01
@suztomo suztomo changed the title ci: stop using maven-central.storage-download.googleapis.com ci: stop using Google's Maven mirror in downstream checks Apr 16, 2026
@suztomo suztomo enabled auto-merge (squash) April 16, 2026 23:05
@suztomo suztomo merged commit 8095342 into googleapis:main Apr 16, 2026
113 checks passed
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.
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.

2 participants