winget-cli

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 56881c83ca40c0c29f7107596791a735d717737e
parent ec7d73b2190d592d5bc480db40115adab2891d01
Author: Flor Chacón <14323496+florelis@users.noreply.github.com>
Date:   Mon, 10 Mar 2025 20:19:09 -0700

Build in parallel (#5283)

Make the pipelines build multiple projects in parallel. In the few tests
I did, there wasn't an improvement larger than the typical variability
there is but there were no issues either, so I'm just gambling that it
may bring some benefit with no proof 🤷‍♀️
###### Microsoft Reviewers: [Open in
CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/microsoft/winget-cli/pull/5283)
Diffstat:
Mazure-pipelines.yml | 4++++
1 file changed, 4 insertions(+), 0 deletions(-)

diff --git a/azure-pipelines.yml b/azure-pipelines.yml @@ -122,6 +122,7 @@ jobs: /p:AppxPackageDir="$(appxPackageDir)" /p:AppxBundle=Always /p:UapAppxPackageBuildMode=SideloadOnly' + maximumCpuCount: true - task: VSBuild@1 displayName: Build Test Project @@ -134,6 +135,7 @@ jobs: /p:AppxPackageDir="$(appxPackageDir)" /p:AppxBundle=Always /p:UapAppxPackageBuildMode=SideloadOnly' + maximumCpuCount: true - task: MSBuild@1 displayName: Build MSIX Test Installer File @@ -145,6 +147,7 @@ jobs: /p:AppxBundle=Never /p:UapAppxPackageBuildMode=SideLoadOnly /p:AppxPackageSigningEnabled=false' + maximumCpuCount: true - task: CopyFiles@2 displayName: 'Copy specific build artifacts' @@ -642,6 +645,7 @@ jobs: solution: '$(solution)' configuration: '$(buildConfiguration)' msbuildArgs: '/bl:$(artifactsDir)\msbuild.binlog' + maximumCpuCount: true - task: CopyFiles@2 displayName: Copy Fuzzing Artifacts for Publishing