Skip to content

Migrate Windows build pools from VS2026 preview scout to production VS2026 image#124902

Open
Copilot wants to merge 2 commits intomainfrom
copilot/migrate-to-vs2026-production
Open

Migrate Windows build pools from VS2026 preview scout to production VS2026 image#124902
Copilot wants to merge 2 commits intomainfrom
copilot/migrate-to-vs2026-production

Conversation

Copy link
Contributor

Copilot AI commented Feb 26, 2026

Switches all Windows agent pool image references from the VS2026 Preview Scout image to the stable production VS2026 image.

Description

  • windows.vs2026preview.scout.amd64windows.vs2026.amd64
  • windows.vs2026preview.scout.amd64.openwindows.vs2026.amd64.open

Files updated:

  • eng/pipelines/common/xplat-setup.yml — official and public Windows build pools
  • eng/pipelines/libraries/fuzzing/deploy-to-onefuzz.yml — fuzzing job pool
  • eng/pipelines/libraries/stress/ssl.yml — SSL stress test pool
  • eng/pipelines/libraries/stress/http.yml — HTTP stress test pool
Original prompt

This section details on the original issue you should resolve

<issue_title>Migrate from VS2026 Preview Scout to production VS2026 build image</issue_title>
<issue_description>We currently use the VS2026 preview scout image (windows.vs2026preview.scout.amd64) across our Windows build pools. Once the production VS2026 image becomes available, we should migrate to it for stability and long-term support.

Likely files to update:

eng/pipelines/common/xplat-setup.yml - Official and public Windows build pools
eng/pipelines/libraries/fuzzing/deploy-to-onefuzz.yml - Fuzzing job pool
eng/pipelines/libraries/stress/ssl.yml - SSL stress test pool
eng/pipelines/libraries/stress/http.yml - HTTP stress test pool

Expected changes:

windows.vs2026preview.scout.amd64 → windows.vs2026.amd64
windows.vs2026preview.scout.amd64.open → windows.vs2026.amd64.open</issue_description>

Comments on the Issue (you are @copilot in this section)

@steveisok https://github.com/dotnet/dotnet/issues/4320 is the VMR counterpart.

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Co-authored-by: akoeplinger <1376924+akoeplinger@users.noreply.github.com>
Copilot AI changed the title [WIP] Migrate from VS2026 preview scout to production build image Migrate Windows build pools from VS2026 preview scout to production VS2026 image Feb 26, 2026
@akoeplinger akoeplinger marked this pull request as ready for review February 26, 2026 15:05
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR migrates Windows build agent pools from the Visual Studio 2026 Preview Scout image to the stable production VS2026 image across the runtime repository's pipeline configuration files. The migration standardizes the build infrastructure by removing preview/scout image references and adopting the production-ready image names that follow the established naming convention for internal (windows.vs2026.amd64) and public (windows.vs2026.amd64.open) build pools.

Changes:

  • Updated image references from windows.vs2026preview.scout.amd64[.open] to windows.vs2026.amd64[.open]
  • Applied consistently across official builds, public builds, and stress/fuzzing test pipelines
  • Affects all Windows-based pipeline jobs in the runtime repository

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
eng/pipelines/common/xplat-setup.yml Updated both official (internal) and public Windows build pool image references to production VS2026
eng/pipelines/libraries/fuzzing/deploy-to-onefuzz.yml Migrated OneFuzz fuzzing deployment job to production VS2026 internal image
eng/pipelines/libraries/stress/ssl.yml Updated SSL stress test Windows job to production VS2026 public image
eng/pipelines/libraries/stress/http.yml Updated HTTP stress test Windows job to production VS2026 public image

@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migrate from VS2026 Preview Scout to production VS2026 build image

3 participants