Update Windows CI builds to multi-agent matrix

This PR updates Windows CI builds to use a multi-agent matrix when
building. Windows 2022 & 2019 have been DISABLED *temporarily* until
we can find a way to automagically detect the location of Visual
Studio build tools.

The only build agent available is Windows 2016, as it works with the
current setup. There is a publishing step, which only runs on the
Windows 2016 agent for now. This solves the issue of multiple
installer artifacts being built when the other agents are
re-enabled.

Per-commit generated binaries remain generated by all (not right now)
Windows build agenst.

Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
This commit is contained in:
Dom Rodriguez 2021-11-04 22:27:55 +00:00
parent 4ed0141389
commit f9c9d56b21
No known key found for this signature in database
GPG Key ID: 72DCF1231E54BD43

View File

@ -9,14 +9,28 @@ trigger:
jobs:
- job: WinBuild
displayName: Windows Build
pool:
vmImage: 'vs2017-win2016'
strategy:
matrix:
Debug:
CI_ENV_BUILD_TYPE: Debug
Release with Release Installer:
CI_ENV_BUILD_TYPE: Release
# windows-2022-Debug:
# imageName: "windows-2022"
# CI_ENV_BUILD_TYPE: Debug
# windows-2022-Release:
# imageName: "windows-2022"
# CI_ENV_BUILD_TYPE: Release
# windows-2019-Debug:
# imageName: "windows-2019"
# CI_ENV_BUILD_TYPE: Debug
# windows-2019-Release:
# imageName: "windows-2019"
# CI_ENV_BUILD_TYPE: Release
windows-2016-Debug:
CI_ENV_BUILD_TYPE: Debug
imageName: "vs2017-win2016"
windows-2016-Release:
CI_ENV_BUILD_TYPE: Release
imageName: "vs2017-win2016"
pool:
vmImage: $(imageName)
steps:
# Gather Dependencies
- task: PowerShell@2