uefi-ref/edk2
1
0
Fork 0
mirror of https://github.com/tianocore/edk2 synced 2026-08-27 00:23:19 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

.azurepipelines: Move to VS2026

Browse source 
This upgrades the Azure Pipelines CI to use
VS2026 instead of VS2022.

The Windows VM image is updated to windows-2025-vs2026 which
has been updated to use VS2026. Note, 2025 references
the Windows Server release, not the VS version. Azure pipelines
has not migrated its windows-2025 VM image to use VS2026 yet,
it will do so after that feature is GA'd, at which point edk2
will have time to update to that VM image.

Signed-off-by: Oliver Smith-Denny <osde@microsoft.com>
This commit is contained in:
Oliver Smith-Denny 2026-06-19 07:24:15 -07:00 • committed by mergify[bot]
parent 0f8d430e52
commit d1b6a9c968
4 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.azurepipelines/ReadMe.md
View file

@ -22,7 +22,7 @@ Focused on building a single target platform and confirming functionality on tha
* Top level CI files should be named `<host os>-<tool_chain>.yml` * Top level CI files should be named `<host os>-<tool_chain>.yml`
* The pipeline YAML file name is referenced in Azure Pipelines. To allow flexibility for toolchain updates in the * The pipeline YAML file name is referenced in Azure Pipelines. To allow flexibility for toolchain updates in the
YAML file without necessitating changes in Azure Pipelines, the toolchain version is not included in the filename. YAML file without necessitating changes in Azure Pipelines, the toolchain version is not included in the filename.
For example, `Windows-VS.yml` is used instead of `Windows-VS2022.yml`. For example, `Windows-VS.yml` is used instead of `Windows-VS2026.yml`.
## Links ## Links

2
.azurepipelines/Windows-VS.yml
View file

@ -25,7 +25,7 @@ variables:
jobs: jobs:
- template: templates/pr-gate-build-job.yml - template: templates/pr-gate-build-job.yml
parameters: parameters:
tool_chain_tag: 'VS2022' tool_chain_tag: 'VS2026'
vm_image: ${{ variables.default_windows_vm }} vm_image: ${{ variables.default_windows_vm }}
arch_list: "IA32,X64" arch_list: "IA32,X64"
usePythonVersion: ${{ variables.default_python_version }} usePythonVersion: ${{ variables.default_python_version }}

2
.azurepipelines/templates/defaults.yml
View file

@ -11,4 +11,4 @@ variables:
default_python_version: "3.12" default_python_version: "3.12"
default_linux_container: "ghcr.io/tianocore/containers/fedora-43-test:b562821" default_linux_container: "ghcr.io/tianocore/containers/fedora-43-test:b562821"
default_linux_vm: "ubuntu-24.04" default_linux_vm: "ubuntu-24.04"
default_windows_vm: "windows-2022" default_windows_vm: "windows-2025-vs2026"

4
.azurepipelines/templates/pr-gate-build-job.yml
View file

@ -117,7 +117,7 @@ jobs:
container: ${{ parameters.container }} container: ${{ parameters.container }}
steps: steps:
# Strip test targets for CI toolchains other than GCC and VS2022, as these # Strip test targets for CI toolchains other than GCC and VS2026, as these
# cannot run them and would be duplicating work during CI if they could. # cannot run them and would be duplicating work during CI if they could.
# Note: Within PR gate CI, NOOPT is only used for building tests. # Note: Within PR gate CI, NOOPT is only used for building tests.
- bash: | - bash: |
@ -147,7 +147,7 @@ jobs:
clean: all clean: all
pool: pool:
vmImage: 'windows-2022' vmImage: 'windows-2025-vs2026'
steps: steps:
- checkout: self - checkout: self