Merge installer repo into SDK

[marcpopMSFT]

• [ ] Copy over issues
• [x] Move the installer repo into a subfolder of SDK
• [x] Figure out how to make it so you can build just the SDK or just the installer side
• [x] Find a home for the installer build page
• [ ] Figure out the cmake requirement so sdk developers don't have to install cmake
• [x] Modify the CI to include the installer legs
• [x] Modify the installer legs to build SDK and tests first (adding 6-10 minutes of time to installer)
• [x] Archive installer repo

Updating as we're doing an initial review of this work for potentially being done it .net 9.

Other scenarios to consider • Installer download page and feed list • Loc build from release branch for SDK and main branch for installer • CPM enabled in SDK • Dependabot and fabric bot in SDK • Workloads are overwritten in the SDK repo (overlaysdkonlkg.targets) • How would this affect stage0 updates and TFM updates? • How does this merge impact SB and VMR? • SDK repo reruns tests, installer repo reruns builds

For local dev build time, I think we need installer to not do it's crossgen build during the plain build. That increases the build time by nearly 2 minutes and if merged into SDK, would be too much to take on. Only do this build during build -pack

[dotnet-issue-labeler[bot]]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[kasperk81]

update process is:

1. runtime, aspnetcore, and x other repositories push their changes to sdk
2. sdk makes a build and pushes to installer
3. installer publishes the daily build

what would be the new process like: "2. sdk publishes the daily build" without step 3 for each successful pr merge?

@mmitche, @mthalman, @MichaelSimons, @lewing, thoughts? it was meant to improve the quality of life of persons investigating issues during sdk to installer updates and, of course, the frequency of daily builds.

[mmitche]

Yes, there would be no step 3 with these improvements.

[kasperk81]

this is completed?

[MiYanni]

I've updated the tasks in the description.

• Issues aren't finished being cleaned up. We have <100 to go through and either close or transfer.
• The CMake requirement has a separate issue created for it.
  • I've resolved this issue, but we still need a better design on how to handle the requirement of CMake.
• I marked "Archive installer repo" as complete since we can't actually archive it until all the servicing branches are out-of-support. For now, we've updated the default branch and have a readme that redirects to the SDK repo.