rever ovn version

[changluyi]

Pull Request

• Make sure you have followed Kube-OVN Code Style.

What type of this PR

Examples of user facing changes:

• Features
• Bug fixes
• Docs
• Tests

Which issue(s) this PR fixes

Fixes #(issue-number)

[gemini-code-assist]

Summary of Changes

Hello @changluyi, 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 aims to enhance the stability and reproducibility of the build process by pinning the OVN dependency to a specific commit. This change ensures that all builds utilize a consistent version of OVN, mitigating potential issues that could arise from using a continuously updated branch.

Highlights

• OVN Version Pinning: The OVN build process has been updated to explicitly check out a specific commit hash (70df1aba7dd36c38905dc643ca709d8e85e541a7) instead of cloning a specific branch.
• Dockerfile Update: The Dockerfile.base now reflects this change, ensuring that the OVN source code used for building is consistently from a known, stable point.

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 reverts the OVN version to a specific commit hash by modifying the Dockerfile. The current implementation uses a full git clone, which is inefficient for Docker builds. My review provides a suggestion to optimize the cloning process to improve build performance and reduce network usage.

[gemini-code-assist]

For build efficiency, it's better to avoid a full git clone. Cloning the entire repository history can significantly slow down the image build process and increase network usage. While a full clone is one way to get a specific commit that isn't at a branch tip, there are more efficient methods.

A better approach is to use a partial clone with --filter=blob:none. This avoids downloading file contents (blobs) until they are needed at checkout, making the initial clone much faster. This feature is supported by the version of Git available in the ubuntu:24.04 base image.

RUN cd /usr/src/ && git clone --filter=blob:none https://github.com/ovn-org/ovn.git && \
    cd ovn && git checkout 70df1aba7dd36c38905dc643ca709d8e85e541a7 && \

[coveralls]

Pull Request Test Coverage Report for Build 19070786628

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 21.541%

---

Totals
Change from base Build 19054987369:	0.0%
Covered Lines:	10940
Relevant Lines:	50787

---

💛 - Coveralls