Optimize Build Jobs

[michael-hawker]

Describe the bug

Currently our WinUI2 build is taking like 90 minutes... 😟

We should split things up to ensure we can have quicker response times on feedback for the CI.

Related issues #66, #133, CommunityToolkit/Tooling-Windows-Submodule#9, (and CommunityToolkit/Tooling-Windows-Submodule#6)

We can try and mitigate this in a few ways:

• Split up building experiments as NuGet packages from rest of build, this does a few things:
  • Means we can have them as a separate dependent job
  • Only build them once
  • Include as artifacts to the build
  • Run tests on them independently
  • In PR, If tests pass, push to a nuget feed so they can be poked while rest of CI builds still more quickly
• Use NuGet packages vs. ProjectReferences in the CI lets us: (ties into Automate Versions of Packages #133)
  • Separate tests out as an independent job for quicker results
  • Separate matrix for each runtime and platform's sample app to build independently as a separate job
    • Hopefully, reduces Memory pressure on CI for ILT0005 Out of memory when building release mode  Tooling-Windows-Submodule#9
• Detect which things have changed ([Build] Experiment detection for intermediate build #66)
  • Only build the new-experiment job if the common/template folders or root config files have changed
  • Have a job which only builds the solution for the experiment(s) that have been modified
    • Only update NuGet package(s) of changed experiments
  • Have a job which builds/tests the infrastructure of labs vs. doing that along with other jobs (if any of it has been touched)
• Smoke Tests - Check packages work on target frameworks (with NuGet packages and scoping above)
  • with new uno templates from dotnet new (Uno.UI & Uno.WinUI)
  • with new base UWP/WinAppSDK templates
  • Check binary package size changes (i.e. measure footprint)

Steps to reproduce

Run build...

Expected behavior

Faster feedback

Screenshots

No response

Code Platform

• UWP
• WinAppSDK / WinUI 3
• Web Assembly (WASM)
• Android
• iOS
• MacOS
• Linux / GTK

Windows Build Number

• Windows 10 1809 (Build 17763)
• Windows 10 1903 (Build 18362)
• Windows 10 1909 (Build 18363)
• Windows 10 2004 (Build 19041)
• Windows 10 20H2 (Build 19042)
• Windows 10 21H1 (Build 19043)
• Windows 11 21H2 (Build 22000)
• Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

• Windows 10, version 1809 (Build 17763)
• Windows 10, version 1903 (Build 18362)
• Windows 10, version 1909 (Build 18363)
• Windows 10, version 2004 (Build 19041)
• Other (specify)

Other SDK version

No response

Visual Studio Version

No response

Visual Studio Build Number

No response

Device form factor

No response

Additional context

No response

Help us help you

Yes, but only if others can assist.