{CI} Bump azdev pin to 0.2.12 for editable installs with --no-build-isolation#33648
Merged
Merged
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @aryasadeghi1, |
️✔️AzureCLI-BreakingChangeTest
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the CI azdev setup pipeline template to pin azdev to a newer azure-cli-dev-tools commit (0.2.12) so editable installs use --no-build-isolation, avoiding extension build failures under newer setuptools behavior.
Changes:
- Bump the
azdevgit pin from the 0.2.11b1 commit to the 0.2.12 commit. - Update inline CI comments to document why the newer pin is needed (notably
--no-build-isolationfor editable installs).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # against the environment instead of an isolated PEP 517 env under | ||
| # setuptools>=79. It is not on PyPI yet; switch this to | ||
| # `pip install --upgrade "azdev==0.2.12"` once published to PyPI. | ||
| pip install --upgrade "git+https://github.com/Azure/azure-cli-dev-tools.git@644d296d9ca9b322b438d5ca21141b247258d0e5#egg=azdev" |
Collaborator
|
CI |
Member
|
@microsoft-github-policy-service rerun |
necusjz
approved these changes
Jun 25, 2026
Member
|
Waiting on this one :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The Codegen Coverage job has been failing since we unpinned
wheel/setuptools. With setuptools 80,azdev extension add "*"builds each extension in an isolated PEP 517 environment, so extensions whosesetup.pyimportsazureat build time (e.g. confcom) fail withModuleNotFoundError: No module named 'azure'.azure-cli-dev-tools 0.2.12 adds
--no-build-isolationto azdev's editable installs, so the build runs against the environment whereazure-cli-coreis already installed. This bumps the pin from 0.2.11b1 (49390f3) to 0.2.12 (644d296).Testing
Installed azdev from the pinned commit and reproduced the pipeline steps locally:
azdev setup -c azure-cli -r azure-cli-extensions, all CLI packages install editable.azdev extension add confcom, succeeds on setuptools 79.x (previously failed with the isolated-build error).azure-cli-extensions already pins the same commit. Once azdev 0.2.11/12 is published to PyPI the pin can switch to
azdev==0.2.11/12.