Skip to content

Fix CG pipeline: update retired windows-2019 image to windows-2022 - #9389

Closed
Sandeep Kumar Das (Sandeep-622) wants to merge 1 commit into
mainfrom
feature/cg-pipeline-image-fix
Closed

Fix CG pipeline: update retired windows-2019 image to windows-2022#9389
Sandeep Kumar Das (Sandeep-622) wants to merge 1 commit into
mainfrom
feature/cg-pipeline-image-fix

Conversation

@Sandeep-622

@Sandeep-622 Sandeep Kumar Das (Sandeep-622) commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Related Issue

No existing GitHub issue — addresses an internal Component Governance compliance action item.

Description

The AdaptiveCards-.NET-Daily pipeline (.pipelines/dotnet-ci.yml) failed at agent allocation:

No image label found to route agent pool Azure Pipelines. Image: windows-2019

The hosted windows-2019 image is retired, so the job never started — the ComponentGovernanceComponentDetection@0 task never ran, leaving the repo non-compliant for Component Governance.

Fix: update the hosted image to a supported one.

 pool:
-  name: Azure Pipelines
-  vmImage: windows-2019
+  vmImage: windows-2022

CI-config-only change; no product/runtime impact. (vmImage alone targets the hosted "Azure Pipelines" pool, so the explicit name line is redundant and was removed.)

Sample Card

Not applicable — pipeline configuration change only.

The AdaptiveCards-.NET-Daily pipeline was failing at agent allocation
('No image label found to route agent pool Azure Pipelines') because
windows-2019 is retired. This prevented the ComponentGovernanceComponentDetection
task from running, leaving the repo non-compliant for Component Governance.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d5865ea7-1d45-40ce-914c-6133278ad620

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Azure Pipelines agent image for the .NET CI pipeline to avoid agent allocation failures caused by the retirement of the windows-2019 hosted image, ensuring the pipeline can run Component Governance detection again.

Changes:

  • Switch the .NET CI pipeline agent image from windows-2019 to windows-2022.
  • Simplify the pool declaration to use only vmImage.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .pipelines/dotnet-ci.yml
Comment thread .pipelines/dotnet-ci.yml
buildPlatform: any cpu

pool:
name: Azure Pipelines

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the only place we need to make the change ?

@Sandeep-622

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants