Skip to content

Commit

Permalink
onebranch: allow publish/package to run in :latest container (#17514)
Browse files Browse the repository at this point in the history
We have to run in an older OneBranch Windows container image due to
compiler bugs.

This change prevents us from having to wait for the container image to
download for build legs that _aren't_ using the compiler.

(cherry picked from commit bc20225)
Service-Card-Id: PVTI_lADOAF3p4s4AmhmszgSI7Rw
Service-Version: 1.21
  • Loading branch information
DHowett committed Aug 23, 2024
1 parent cf7a661 commit b028a57
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -106,6 +106,11 @@ extends:
- stage: Build
displayName: Build
dependsOn: []
variables:
# This was set by the parent build, but we need to override it to select a specific compiler version
- template: ./build/pipelines/templates-v2/variables-onebranch-config.yml@self
parameters:
containerVersion: 1.0.02566.28
jobs:
- template: ./build/pipelines/templates-v2/job-build-project.yml@self
parameters:
Expand Down
7 changes: 6 additions & 1 deletion build/pipelines/templates-v2/variables-onebranch-config.yml
Original file line number Diff line number Diff line change
@@ -1,2 +1,7 @@
parameters:
- name: containerVersion
type: string
default: latest

variables:
WindowsContainerImage: 'onebranch.azurecr.io/windows/ltsc2022/vse2022:1.0.02566.28'
WindowsContainerImage: 'onebranch.azurecr.io/windows/ltsc2022/vse2022:${{ parameters.containerVersion }}'

0 comments on commit b028a57

Please sign in to comment.