{CI} Speed up CLI linter and style checks with multicore agents#31688
{CI} Speed up CLI linter and style checks with multicore agents#31688
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @bebound, |
️✔️AzureCLI-BreakingChangeTest
|
|
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>
|
There was a problem hiding this comment.
Pull Request Overview
This PR speeds up the execution of the CLI linter and style checks by switching from a single-core pool (ubuntu_pool) to a multi-core pool (ubuntu_multi_core_pool) for improved performance.
- Replaces the pool used for the "Check CLI Style" job
- Replaces the pool used for the "Check CLI Linter" job
| timeoutInMinutes: 120 | ||
| pool: | ||
| name: ${{ variables.ubuntu_pool }} | ||
| name: ${{ variables.ubuntu_multi_core_pool }} |
There was a problem hiding this comment.
Why is the multi-core agent pool not used before?
There was a problem hiding this comment.
The multicore agent was initially created specifically for running rpm/deb tests, as they exceed the 2 hours timeout, and did not consider being used for azdev style.
Description
Use multicore agent for these tests to speed up the CI. The ultimate solution is using
ruff.Ref:
https://dev.azure.com/azclitools/public/_build/results?buildId=254153&view=logs&jobId=168ccbe3-da49-5c0b-6478-08f7016e4bf5&j=36dd4138-4d53-5e46-00d9-e5cd9744be05
https://dev.azure.com/azclitools/public/_build/results?buildId=254279&view=logs&j=168ccbe3-da49-5c0b-6478-08f7016e4bf5