[CI] Update images to 20260213-110714-021547fe

[mshr-h]

Update the CI docker images to include Python 3.10
Part of #18682

[gemini-code-assist]

Summary of Changes

Hello @mshr-h, I'm Gemini Code Assist¹! 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 focuses on a critical infrastructure update for the continuous integration system. It refreshes the Docker images used across various CI environments to a newer version. This update is essential for enabling support for Python 3.10 within the CI pipelines, ensuring that future development and testing can leverage this Python version.

Highlights

• CI Docker Image Update: The CI Docker images have been updated to a new version, 20260213-110714-021547fe, across all configurations (ARM, CPU, GPU, Lint, WASM).
• Python 3.10 Support: This update specifically incorporates Python 3.10 into the CI Docker images, addressing a requirement from issue [Tracking Issue] Upgrade Python to 3.10 #18682.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• ci/jenkins/docker-images.ini
  • Updated all ci_arm, ci_cpu, ci_gpu, ci_lint, and ci_wasm Docker image tags to 20260213-110714-021547fe.

Activity

• No specific review comments or activities have been recorded for this pull request yet.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the CI docker image tags in ci/jenkins/docker-images.ini. The change is straightforward and aligns with the goal of using new images that include Python 3.10. I have provided one suggestion to improve the maintainability of this configuration file by reducing redundancy, which could make future updates easier.

[gemini-code-assist]

To improve maintainability and reduce redundancy, consider defining the image tag as a variable and reusing it. This would make future updates easier and reduce the chance of inconsistencies. For example, you could add a ci_tag variable under the [jenkins] section and reference it:

ci_tag: 20260213-110714-021547fe
ci_arm: tlcpack/ci-arm:${ci_tag}
ci_cpu: tlcpack/ci_cpu:${ci_tag}
ci_gpu: tlcpack/ci-gpu:${ci_tag}
ci_lint: tlcpack/ci-lint:${ci_tag}
ci_wasm: tlcpack/ci-wasm:${ci_tag}

This change would depend on the parser for this file supporting variable interpolation. If that's not feasible, the current explicit approach is acceptable.

[yongwww]

Nice to have.