[release/7.0] Port workload fixes from 6.0

[joeloff]

• The updated task now provides metadata that will allow us to split the VSDROP generation into two separate archives. One which only contains workload packs (needed to share DROPs across VS versions to support multi-targeting) and another that only contains the manifest installers and workload components.
• The ZIP archive names have been updated to disambiguate its contents and support automatic drop creation during staging.

Most of the changes are in eng due to the Arcade update to obtain the latest copy of the workload build tasks. Those changes are unrelated to the workload fix, but appears to be necessary.

[ghost]

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.

[lewing]

worload changes lgtm, someone else should look over the arcade related stuff

[ghost]

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

Issue Details

---

• The updated task now provides metadata that will allow us to split the VSDROP generation into two separate archives. One which only contains workload packs (needed to share DROPs across VS versions to support multi-targeting) and another that only contains the manifest installers and workload components.
• The ZIP archive names have been updated to disambiguate its contents and support automatic drop creation during staging.

Most of the changes are in eng due to the Arcade update to obtain the latest copy of the workload build tasks. Those changes are unrelated to the workload fix, but appears to be necessary.

Author:	joeloff
Assignees:	joeloff
Labels:	area-Infrastructure
Milestone:	-

[carlossanlop]

@joeloff are these types of changes considered tell-mode or ask-mode? If it's the latter, we need M2 approval. If the former, I can sign-off.

[lewing]

this is build infrastructure supporting workload insertion and is tell mode as discussed in tactics

[carlossanlop]

Ok thanks, @lewing (I wasn't sure, I had not seen changes related to distros before).

There are a lot of failures. Are any of them related to this? @joeloff

[lewing]

The failures aren't because of the workload stuff, it looks like it is the sdk bump causing problems.

@marcpopMSFT is this because the SDK bumped the 6.0.x runtime?

[lewing]

This can probably wait until servicing has gone out

[hoyosjs]

How come nested in a p directory?

[hoyosjs]

Is it to avoid path length issues?

[joeloff]

yup, p => packs, c => components... We've introduced additional naming elements for multitargeting and if we ever do SxS preview feature bands, then the package IDs can get quite long so I'm just avoiding things early on. And we already include the packs and component parts in the final artifact name, but we need separate folders to zip things up insolation.

[carlossanlop]

This can probably wait until servicing has gone out

Meaning this should wait until after the RC2 snap?

[joeloff]

This can probably wait until servicing has gone out

Meaning this should wait until after the RC2 snap?

That's fine, as long as we get this into RC2 after the snap otherwise we're going to have to go through all the manual work again for VS.

[carlossanlop]

There's a conflict. @joeloff can you please resolve it?

[joeloff]

There's a conflict. @joeloff can you please resolve it?

Done. I picked the RC1 SDK since that's what darc pulled in as part of the Arcade update.

[carlossanlop]

That's fine, as long as we get this into RC2 after the snap otherwise we're going to have to go through all the manual work again for VS.

Thanks @joeloff. I added the "no merge" label. Please remove it when this is ready to merge after the snap, and ping me.

[lewing]

failure is unrelated

[joeloff]

Verified a signed internal build and everything looks as expected.

[lewing]

failures are not related

      MSBuild version 17.4.0-preview-22416-02+5d102ae37 for .NET
      /datadisks/disk1/work/B5AA0966/p/wasm-test-runner/WasmTestRunner.proj : error : Failed to resolve SDK 'Microsoft.Build.NoTargets/3.5.0'. Package restore was successful but a package with the ID of "Microsoft.Build.NoTargets" was not installed.
      /datadisks/disk1/work/B5AA0966/p/wasm-test-runner/WasmTestRunner.proj : error MSB4236: The SDK 'Microsoft.Build.NoTargets/3.5.0' specified could not be found.
      Test Harness Exitcode is : 1
      To run the test:
      > set CORE_ROOT=/datadisks/disk1/work/B5AA0966/p
      > /datadisks/disk1/work/B5AA0966/w/A7060920/e/JIT/HardwareIntrinsics/X86/Avx2/LoadAlignedVector256NonTemporal_ro/LoadAlignedVector256NonTemporal_ro.sh

[hoyosjs]

Failures are #75391 and PinObj_neg doesn't seem to have an associated issue, but there's other runs with the same failure mode - the output doesn't get more descriptive than Test Harness Exitcode is : 1 and there's not much to go by nonetheless... Merging this as tell mode for workloads work. cc: @jeffschwMSFT @marek-safar