[release/6.0] source-build: support building runtime using non-portable runtime packages (backport of #75597)

[ayakael]

Backport of #75597

Per @tmds

Currently source-build performs a 'runtime-portable' build that produces 'linux-{arch}' packages that are used when building target runtime (non-portable).

With this change, we can use the non-portable packages that are produced by a previous (non-portable) 'runtime' build. This helps eliminate the 'runtime-portable' build.

Customer impact

For distro maintainers, this removes the need for providing portable runtime packages to build non-portable runtime, thus we do not need to build runtime twice. This reduces our build time significantly.

Testing

• unit tests in ci
• source-build build within Alpine environment passes
• Installer backport: [release/6.0.1xx] Eliminate runtime portable build installer#14816

Risk

Low, as it is already in main, and only activates when DotNetBuildFromSource=true

[dotnet-issue-labeler]

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

[carlossanlop]

@ViktorHofer I see you approved the main PR. This is an infra change only, so tell-mode. Can you please sign off this backport?

[ViktorHofer]

Apart from one nit change, LGTM

[carlossanlop]

Two tests are failing with a nuget problem. @ViktorHofer @ayakael Is the failure related to this change?

• Queue: Build Browser wasm Release AllSubsets_Mono_RuntimeTests
• Tests: JIT.CodeGenBringUpTests and JIT.jit64
• Log file: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-77509-merge-435b1597369e479bb9/JIT.CodeGenBringUpTests/1/console.b29c28be.log?helixlogtype=result
  Failure message:

/datadisks/disk1/work/9D6508C9/p/wasm-test-runner/WasmTestRunner.proj : error MSB4242: SDK Resolver Failure: "The SDK resolver "NuGetSdkResolver" failed while attempting to resolve the SDK "Microsoft.Build.NoTargets/1.0.53". Exception: "System.IO.IOException: The system cannot open the device or file specified. : 'NuGet-Migrations'

[ayakael]

Two tests are failing with a nuget problem. @ViktorHofer @ayakael Is the failure related to this change?

• Queue: Build Browser wasm Release AllSubsets_Mono_RuntimeTests
• Tests: JIT.CodeGenBringUpTests and JIT.jit64
• Log file: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-77509-merge-435b1597369e479bb9/JIT.CodeGenBringUpTests/1/console.b29c28be.log?helixlogtype=result
  Failure message:

/datadisks/disk1/work/9D6508C9/p/wasm-test-runner/WasmTestRunner.proj : error MSB4242: SDK Resolver Failure: "The SDK resolver "NuGetSdkResolver" failed while attempting to resolve the SDK "Microsoft.Build.NoTargets/1.0.53". Exception: "System.IO.IOException: The system cannot open the device or file specified. : 'NuGet-Migrations'

I don't see how it could be related given that this change only expresses itself when DotNetBuildFromSource=true. That test doesn't seem to set that flag.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #75597

Per @tmds

Currently source-build performs a 'runtime-portable' build that produces 'linux-{arch}' packages that are used when building target runtime (non-portable).

With this change, we can use the non-portable packages that are produced by a previous (non-portable) 'runtime' build. This helps eliminate the 'runtime-portable' build.

Customer impact

For distro maintainers, this removes the need for providing portable runtime packages to build non-portable runtime, thus we do not need to build runtime twice. This reduces our build time significantly.

Testing

• unit tests in ci
• source-build build within Alpine environment passes
• Installer backport: [release/6.0.1xx] Eliminate runtime portable build installer#14816

Risk

Low, as it is already in main, and only activates when DotNetBuildFromSource=true

Author:	ayakael
Assignees:	-
Labels:	area-Infrastructure, community-contribution
Milestone:	6.0.x

[ViktorHofer]

@carlossanlop can this change be merged into release/6.0? Is the branch already open?