Join points and product parity

[mmitche]

It is highly likely that Microsoft's .NET build will need some kind of join point where outputs from multiple build environments are required to produce other outputs needed to ship to customers. Note: This is not an option for our Linux distro partners. Cases might include NuGet packages that have native assets from multiple OSs in them, for instance. We need to identify what this set of assets is, and how it will be built.

Requirements:

• Join point job(s) can be run in both the isolated repo build as well as the full VMR build. The idea here is that we should be able to validate the join without doing a full VMR build.
• Join point job(s) must be at the end of the full product build.
• Support VMR build graph depth of >= 2. The depth might only be two but infrastructure should support a deeper graph.

T-Shirt Size: XL

Work Items

Infrastructure:

• [VMR] Merge artifacts and packages pipeline artifacts payloads #4215
• [VMR] Include vertical manifest in the vertical artifacts payload #4216
• [VMR] Add BuildPass parameter to vmr-build.yml #4217
• [VMR] Add support for join point vertical job in vmr-build.yml #4218
• Implement the spec to define projects as part of a join vertical in a unified build arcade#15098

Join points/product parity issues in repos:

• Create first pass 2 stage and job #4633
• Determine what to do with cross-apphosts in installer MSI builds #4114
• Determine how to build aspnetcore's hosting bundle aspnetcore#52884
• Build workloads in the VMR #3904
• Determine how to build the SdkLocator and VSTemplateLocator in the VMR #4336
• Enable IBC optimization for repos that need it #4041
• Build the Cross-OS DAC in the VMR #4631
• Build (just) the sdk bundle in sdk BuildPass=2 for win-x64, win-x86, win-arm64 #4777

[mmitche]

T-Shirt Size: XL

I think there will be quite a lot of messiness to unpack here.

[ViktorHofer]

Closing this epic as all join point components got implemented. Also, we shouldn't be missing any packages from the VMR anymore.
🎉🎉🎉