{CI} Update Azure Pipelines to use Ubuntu 22.04 pools #30996
+12
−8
Conversation
This file contains 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
️✔️AzureCLI-FullTest
|
️✔️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>
|
microsoft-github-policy-service
bot
requested review from
yonzhan,
jiasli,
jsntcy,
bebound and
Pan-Qi
wangzelin007
commented
Mar 10, 2025
| @@ -1,6 +1,6 @@ | |||
| variables: | |||
| ubuntu_pool: 'pool-ubuntu-2004' | |||
| ubuntu_multi_core_pool: 'pool-ubuntu-2004-multi-core' | |||
| ubuntu_pool: 'pool-ubuntu-2204' | |||
There was a problem hiding this comment.
The reason for not using pool-ubuntu-latest is that Azure PowerShell team has already created pool-ubuntu-2204.
There was a problem hiding this comment.
What's the ubuntu version in pool-ubuntu-latest-multi-core, 22.04 or 24.04?
There was a problem hiding this comment.
22.04，because 2204 is the latest one in 1ES image.
There was a problem hiding this comment.
That's a pretty old image. I prefer to change the PR title to 22.04 instead of latest.
In general, latest should refer to 24.04, which was released 1 year ago.
3 tasks
wangzelin007
force-pushed
the
wzl/drop-ubuntu-2004-ado
branch
from
3d1957c to
47ed94f
Compare
wangzelin007
commented
Mar 10, 2025
| @@ -27,10 +27,10 @@ parameters: | |||
| default: | |||
| - name: AMD64 | |||
| value: amd64 | |||
| pool: pool-ubuntu-2004-multi-core | |||
| pool: pool-ubuntu-latest-multi-core | |||
There was a problem hiding this comment.
I have already tried using variables in the parameters, but Azure Pipelines gives this error:
There was a problem hiding this comment.
Haha, that's why I don't use variable here previously.
bebound
approved these changes
Mar 12, 2025
wangzelin007
changed the title
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.
Related command
Description
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.