Skip to content

Fix docker-image-refresh: use a Windows pool for the 1ES SDL stage #3669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ramsessanchez merged 1 commit into from
Jul 21, 2026
+7 −4
Merged

Fix docker-image-refresh: use a Windows pool for the 1ES SDL stage #3669

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions .azure-pipelines/docker-image-refresh.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,9 @@
name: $(Date:yyyyMMdd)$(Rev:.r)_docker-image-refresh

parameters:
- name: WindowsPool
type: string
default: 1es-windows-ps-compute-m
- name: LinuxPool
type: string
default: Azure-Pipelines-1ESPT-ExDShared
Expand Down Expand Up @@ -47,10 +50,10 @@ resources:
extends:
template: v1/1ES.Official.PipelineTemplate.yml@1ESPipelineTemplates
parameters:
pool:
name: ${{ parameters.LinuxPool }}
image: ubuntu-latest
os: linux
# The 1ES template injects an SDL/compliance stage that MUST run on a Windows pool, so the
# template-level pool is Windows. The actual container build overrides to a Linux pool at the
# job level below. (Same pattern as sdk-release.yml.)
pool: ${{ parameters.WindowsPool }}
settings:
networkIsolationPolicy: Permissive
customBuildTags:
Expand Down
Loading