From f9c9d56b21e2eda7dd620b5f2f35aa0a4f5d7ce8 Mon Sep 17 00:00:00 2001 From: Dom Rodriguez Date: Thu, 4 Nov 2021 22:27:55 +0000 Subject: [PATCH] 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 --- azure-pipelines.yml | 26 ++++++++++++++++++++------ 1 file changed, 20 insertions(+), 6 deletions(-) diff --git a/azure-pipelines.yml b/azure-pipelines.yml index e34a3bc5..fde90697 100644 --- a/azure-pipelines.yml +++ b/azure-pipelines.yml @@ -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