[PR #1396] [CLOSED] Enhance Windows CI builds #1807

New issue

Closed

opened 2026-05-05 08:02:19 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 08:02:19 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/debauchee/barrier/pull/1396
Author: @shymega
Created: 11/5/2021
Status: ❌ Closed

Base: master ← Head: enhancement/builds/windows-multi-versions-build

📝 Commits (1)

f9c9d56 Update Windows CI builds to multi-agent matrix

📊 Changes

1 file changed (+20 additions, -6 deletions)

View changed files

📝 azure-pipelines.yml (+20 -6)

📄 Description

This PR adds support for the Windows Server 2022 build agent. This isn't based on Windows 11, but rather Windows 10. I added 2022, 2019, and 2016 to a build matrix. Currently, 2022 and 2016 are disabled.

I had to do that because currently they fail to build, as the BATCH script has the VS SDK path hardcoded. Until we fix that, the aforementioned build agents will remain disabled.

## Contributor Checklist:

I have created a file in the doc/newsfragments directory (and read the README.md in that directory)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/debauchee/barrier/pull/1396 **Author:** [@shymega](https://github.com/shymega) **Created:** 11/5/2021 **Status:** ❌ Closed **Base:** `master` ← **Head:** `enhancement/builds/windows-multi-versions-build` --- ### 📝 Commits (1) - [`f9c9d56`](https://github.com/debauchee/barrier/commit/f9c9d56b21e2eda7dd620b5f2f35aa0a4f5d7ce8) Update Windows CI builds to multi-agent matrix ### 📊 Changes **1 file changed** (+20 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `azure-pipelines.yml` (+20 -6) </details> ### 📄 Description This PR adds support for the Windows Server 2022 build agent. This isn't based on Windows 11, but rather Windows 10. I added 2022, 2019, and 2016 to a build matrix. Currently, 2022 and 2016 are disabled. I had to do that because currently they fail to build, as the BATCH script has the VS SDK path hardcoded. Until we fix that, the aforementioned build agents will remain disabled. `##` Contributor Checklist: * [x] I have created a file in the `doc/newsfragments` directory (and read the `README.md` in that directory) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>