{CI} Add artifact publishing for built wheels in CI pipeline#9067
{CI} Add artifact publishing for built wheels in CI pipeline#9067wangzelin007 merged 1 commit intoAzure:mainfrom
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @wangzelin007, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
microsoft-github-policy-service
bot
requested review from
Pan-Qi,
bebound,
jiasli,
jsntcy,
kairu-ms and
yonzhan
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the CI pipeline to publish built extension wheels as artifacts. The changes enable automatic collection and publishing of wheel files generated during testing, making them available for download or further processing in the CI/CD pipeline.
- Adds environment variable support to export built wheels to a designated output directory
- Implements artifact publishing task in Azure DevOps pipeline for wheel files
- Includes error handling and logging for the wheel export process
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| scripts/ci/test_source.py | Adds logic to copy built wheels to an output directory when WHEELS_OUTPUT_DIR environment variable is set |
| azure-pipelines.yml | Configures the pipeline to set WHEELS_OUTPUT_DIR and publish wheels as pipeline artifacts |
| inputs: | ||
| targetPath: '$(Build.ArtifactStagingDirectory)/wheels-$(python.version)' | ||
| artifact: 'wheels-$(python.version)' | ||
| publishLocation: 'pipeline' |
There was a problem hiding this comment.
[nitpick] Consider adding a condition to only publish artifacts when the wheels directory exists and contains files. This would prevent publishing empty artifacts when no wheels are built or when WHEELS_OUTPUT_DIR is not set.
|
This PR uploads all candidate wheels to Azure DevOps pipeline artifacts for testing.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.