Collapse Mono builds into single builds for Desktop targets

[safern]

Currently we fan out test legs and build Mono and Libraries in a separate leg. Then put those together in a run test leg and submit to helix. We do similar things for the mono runtime tests.

However this model has proven that reliability issues like networking hiccups, artifacts service outages, etc, bite us and the gain in time for Mono targets is not worth it.

We should be collapsing the Mono desktop targets into single legs that build Mono, Libraries, Tests and submit to helix, similar to how we do it for Android, WASM, iOS. That will reduce the number of legs we have on CI and improve reliability for those legs on infra issues.

I will take care of collapsing the libraries tests legs, @naricc could you help collapsing the runtime ones? I guess this would replace: #43952

cc: @akoeplinger @ViktorHofer

[Dotnet-GitSync-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.

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Currently we fan out test legs and build Mono and Libraries in a separate leg. Then put those together in a run test leg and submit to helix. We do similar things for the mono runtime tests.

However this model has proven that reliability issues like networking hiccups, artifacts service outages, etc, bite us and the gain in time for Mono targets is not worth it.

We should be collapsing the Mono desktop targets into single legs that build Mono, Libraries, Tests and submit to helix, similar to how we do it for Android, WASM, iOS. That will reduce the number of legs we have on CI and improve reliability for those legs on infra issues.

I will take care of collapsing the libraries tests legs, @naricc could you help collapsing the runtime ones? I guess this would replace: #43952

cc: @akoeplinger @ViktorHofer

Author:	safern
Assignees:	naricc
Labels:	area-Infrastructure-mono, untriaged
Milestone:	-

[naricc]

Yes. I will help with the runtime ones. So this basically means that all the mono legs should be using the global-build-job.yml?

Also any preference if I fix this at the same time as #43952 or in seperate PRs?

[safern]

Yeah, that means they should use the global build template. Just like the Android and Browser runtime tests.

I think it needs to be on a same PR so that we don't have to build coreclr as part of that job.

[ViktorHofer]

@naricc were you able to look into this?

[naricc]

@ViktorHofer Sorry, I haven't made any progress on this; its been a lower priority item for me that I keep meaning to get to.

[SamMonoRT]

Not going to get to it in 6.0, moving to 7.0.0. We might consider this after RC1 if we have spare cycles.