Conversation
…ipeline Replace MSSecurity-1ES-Build-Agents-Pool with vmImage: windows-latest for all PR validation jobs (build_test, build_test_dev, spotbugs, lint). These jobs build MSAL only and do not require the 1ES self-hosted pool.
|
❌ Work item link check failed. Description does not contain AB#{ID}. Click here to Learn more. |
There was a problem hiding this comment.
Pull request overview
Updates the Azure Pipelines PR validation configuration to run MSAL PR checks on Microsoft-hosted Windows agents instead of the MSSecurity-1ES self-hosted pool, simplifying agent dependency requirements for the PR pipeline.
Changes:
- Switch pipeline
poolfromMSSecurity-1ES-Build-Agents-Poolto Microsoft-hostedvmImage: 'windows-latest'.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
✅ Work item link check complete. Description contains link AB#3549891 to an Azure Boards work item. |
fadidurah
left a comment
There was a problem hiding this comment.
I'm not actually sure if this will work lol I think we added these to 1ES pool for a reason, but if the checks don't fail, LGTM
IIRC we need them when we build broker for some weird reason, publications and 1es pipelines |
Summary
Replace
MSSecurity-1ES-Build-Agents-Poolwith Microsoft-hostedvmImage: 'windows-2022'in thepr-msal.ymlpipeline.Changes
azure-pipelines/pull-request-validation/pr-msal.ymlpool: { name: MSSecurity-1ES-Build-Agents-Pool, image: MSSecurity-1ES-Windows-2022, os: windows }pool: { vmImage: 'windows-2022' }Affected Jobs
All 4 PR validation jobs now run on Microsoft-hosted agents:
None of these jobs build Broker or require self-hosted agent capabilities.
AB#3549891