Skip to content

Conversation

@kabir
Copy link
Collaborator

@kabir kabir commented Nov 4, 2025

openjdk:17-slim has disappeared

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @kabir, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves an issue where the openjdk:17-slim Docker image, previously used for multi-instance replicated queue manager tests, became unavailable. By switching to mirror.gcr.io/eclipse-temurin:17-jre-jammy, the PR ensures that these critical tests can continue to build and run successfully, maintaining the stability of the test environment.

Highlights

  • Base Docker Image Update: The base Docker image for the multi-instance replicated queue manager tests has been updated to address the unavailability of the previous image.
  • Image Replacement: The openjdk:17-slim image, which was no longer available, has been replaced with mirror.gcr.io/eclipse-temurin:17-jre-jammy in the relevant Dockerfiles.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
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 resolves a build failure caused by the disappearance of the openjdk:17-slim Docker image by switching to mirror.gcr.io/eclipse-temurin:17-jre-jammy. The change is correct and addresses the issue. My review includes suggestions to pin the base image to a specific version using an immutable tag. This will improve the stability and reproducibility of your test builds. For future consideration, you might want to centralize the base image definition to avoid duplication across the two Dockerfiles.

@@ -1,4 +1,4 @@
FROM openjdk:17-slim
FROM mirror.gcr.io/eclipse-temurin:17-jre-jammy
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

To ensure reproducible builds, it's a good practice to use a specific, immutable image tag instead of a floating tag like 17-jre-jammy. Floating tags can be updated, potentially introducing unexpected changes or breaking the build. Using a more specific version tag will make your test environment more stable and predictable.

FROM mirror.gcr.io/eclipse-temurin:17.0.11_9-jre-jammy

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ignoring since we don't really do this in other places

@@ -1,4 +1,4 @@
FROM openjdk:17-slim
FROM mirror.gcr.io/eclipse-temurin:17-jre-jammy
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

To ensure reproducible builds, it's a good practice to use a specific, immutable image tag instead of a floating tag like 17-jre-jammy. Floating tags can be updated, potentially introducing unexpected changes or breaking the build. Using a more specific version tag will make your test environment more stable and predictable.

FROM mirror.gcr.io/eclipse-temurin:17.0.11_9-jre-jammy

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ignoring since we don't really do this in other places

@kabir kabir merged commit e2eba4e into a2aproject:main Nov 4, 2025
10 checks passed
kabir added a commit that referenced this pull request Nov 4, 2025
kabir added a commit to kabir/a2a-java that referenced this pull request Dec 23, 2025
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.

1 participant