Disable build isolation for workflow tarball by default

[shunping]

Also add an environment variable USE_BUILD_ISOLATION_FOR_WORKFLOW to enable it if needed.

Internal bug id: 475376468

[gemini-code-assist]

Summary of Changes

Hello @shunping, 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 modifies the Python container's boot logic to adjust how Python packages are installed, specifically targeting workflow tarballs. The primary goal is to disable pip's build isolation feature by default for these installations, which can sometimes cause issues or overhead. To maintain configurability, an environment variable has been added, allowing users to easily re-enable build isolation if their specific workflow requires it. This change provides a more controlled and potentially more efficient installation environment for Python workflows.

Highlights

• Default Build Isolation Change: Build isolation for workflow tarball installations is now disabled by default, aiming to streamline the installation process.
• Environment Variable for Override: An environment variable, USE_BUILD_ISOLATION_FOR_WORKFLOW, has been introduced. Setting this variable will re-enable build isolation for workflow tarball installations, providing flexibility for specific use cases.
• Refactored pipInstallPackage: The pipInstallPackage function now accepts a useBuildIsolation boolean parameter, allowing explicit control over whether the --no-build-isolation flag is passed to pip install commands. Other pip install calls (for extra packages and SDK) explicitly enable build isolation.

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

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

[shunping]

R: @tvalentyn

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

[tvalentyn]

I would also introduce a variable NO_BUILD_ISOLATION or PIP_NO_BUILD_ISOLATION in case it comes up again for other scenarios, so users can disable build isolation across the board for any pip installation command.