emsdk packages missing from the VMR

[ViktorHofer]

The following packages get produced in a MSFT build but not from the VMR:

Missing

Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.linux-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.linux-musl-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.linux-musl-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.linux-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.osx-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.osx-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.win-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.win-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.linux-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.linux-musl-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.linux-musl-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.linux-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.osx-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.osx-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.win-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.win-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Python.osx-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Python.osx-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Python.win-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Python.win-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.linux-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.linux-musl-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.linux-musl-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.linux-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.osx-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.osx-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.win-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.win-x64

Expected

The following are expected and will be added with the ongoing workloads work done by @akoeplinger:

Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.win-arm64.Msi.arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.win-x64.Msi.x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.win-arm64.Msi.arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.win-x64.Msi.x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Python.win-arm64.Msi.arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Python.win-x64.Msi.x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.win-arm64.Msi.arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.win-x64.Msi.x64
Microsoft.NET.Workload.Emscripten.Current.Manifest-10.0.100-preview.3.Msi.arm64
Microsoft.NET.Workload.Emscripten.Current.Manifest-10.0.100-preview.3.Msi.x64
Microsoft.NET.Workload.Emscripten.Current.Manifest-10.0.100-preview.3.Msi.x86
Microsoft.NET.Workload.Emscripten.net6.Manifest-10.0.100-preview.3.Msi.arm64
Microsoft.NET.Workload.Emscripten.net6.Manifest-10.0.100-preview.3.Msi.x64
Microsoft.NET.Workload.Emscripten.net6.Manifest-10.0.100-preview.3.Msi.x86
Microsoft.NET.Workload.Emscripten.net7.Manifest-10.0.100-preview.3.Msi.arm64
Microsoft.NET.Workload.Emscripten.net7.Manifest-10.0.100-preview.3.Msi.x64
Microsoft.NET.Workload.Emscripten.net7.Manifest-10.0.100-preview.3.Msi.x86
Microsoft.NET.Workload.Emscripten.net8.Manifest-10.0.100-preview.3.Msi.arm64
Microsoft.NET.Workload.Emscripten.net8.Manifest-10.0.100-preview.3.Msi.x64
Microsoft.NET.Workload.Emscripten.net8.Manifest-10.0.100-preview.3.Msi.x86
Microsoft.NET.Workload.Emscripten.net9.Manifest-10.0.100-preview.3.Msi.arm64
Microsoft.NET.Workload.Emscripten.net9.Manifest-10.0.100-preview.3.Msi.x64
Microsoft.NET.Workload.Emscripten.net9.Manifest-10.0.100-preview.3.Msi.x86
emsdk/10.0.0-preview.3.25155.1/workloads/Workload.VSDrop.emsdk.10.0-10.0.100-preview.3-pre.components.zip
emsdk/10.0.0-preview.3.25155.1/workloads/Workload.VSDrop.emsdk.10.0-10.0.100-preview.3.components.zip
emsdk/10.0.0-preview.3.25155.1/workloads/Workload.VSDrop.emsdk.10.0-10.0.100-preview.3.packs.zip

[ViktorHofer]

Posting a few snippets from an offline conversation:

emsdk is the only repository that produces artifacts that get published (released) by the staging pipeline but don't get built & published inside the VMR (Is this true?). This sounds a bit counter-intuitive to me. Let's chat about why that's the case.

If we would build emsdk in the VMR, we would always build, sign and publish the following assets on win-x64 (which is the long pole today):

Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.win-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.win-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Python.win-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Python.win-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.win-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Node.win-x64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.win-arm64
Microsoft.NET.Runtime.Emscripten.3.1.56.Cache.win-x64

[mmitche]

May be required in p4. The operative question is whether this needs to be built monthly? We ship monthly right now, but why? @lewing

[lewing]

We do make small changes as required that flow into emsdk.