[DP-19090] Migrate Windows CI jobs from Windows 2019 to Windows 2025#3406
Conversation
Switch both Windows-pool references from s1-prod-windows (Windows 2019) to s1-windows-2025-amd64-4 (Windows 2025): - .semaphore/semaphore.yml: the 'Windows x64 Stable: Tests' block that runs on PR pushes. - .semaphore/playwright-e2e.yml: the parameterized Windows E2E pipeline (manual / scheduled task). Per the Builds team Windows 2025 rollout.
There was a problem hiding this comment.
Pull request overview
Migrates the two Windows Semaphore CI agent pool references from the aging s1-prod-windows (Windows Server 2019) to s1-windows-2025-amd64-4 (Windows Server 2025), aligning with the org-wide rollout to a supported baseline OS image.
Changes:
- Update Windows stable test block agent type in
.semaphore/semaphore.yml. - Update Windows Playwright E2E block agent type in
.semaphore/playwright-e2e.yml.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.semaphore/semaphore.yml |
Switches PR-gated Windows x64 Stable Tests block to the Windows Server 2025 pool. |
.semaphore/playwright-e2e.yml |
Switches parameterized/scheduled Windows Playwright E2E block to the Windows Server 2025 pool. |
|
|
|
🤖 Review Hub assignments
Scoring breakdown for Dave Shoup (@shouples)
Generated by Review Hub. This comment is rewritten on each (re)assignment. |





Change Description
Migrates the two Windows pool references in this repo from
s1-prod-windows(Windows Server 2019) tos1-windows-2025-amd64-4(Windows Server 2025):.semaphore/semaphore.yml— theWindows x64 Stable: Testsblock (runs on PR pushes; gated only by the release-markerskip:clause that does not apply to this change)..semaphore/playwright-e2e.yml— the parameterizedWindows x64: Playwright E2E Testsblock (manual / scheduled task pipeline).Why this is the right change:
s1-windows-2025-amd64-4pool is already provisioned and was first exercised in the semaphore-test canary.Why this is safe:
agent.machine.type; no commands, prologue, dependencies, or job structure are modified.npm,npx,choco,gh, andmake— all toolchain-portable and not pinned to a specific Windows SDK version.Testing
Windows x64 Stable: Testsblock insemaphore.ymlwill run on this PR (theskip:only fires onrelease.svg/.versions/next.txtchanges, neither of which are touched here). Look for that block to pass on the new agent.playwright-e2e.ymlis parameterized and not triggered on PR; it will be exercised the next time the manual/scheduled task runs after merge.