V3 publishing

[epananth]

Use V3 publishing for runtime

Test with default channel => https://dev.azure.com/dnceng/internal/_build/results?buildId=802296&view=results
Test without default channel => https://dev.azure.com/dnceng/internal/_build/results?buildId=802367&view=results

[ghost]

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

[ViktorHofer]

@epananth @mmitche can/should the post build checks also be moved into the outer ring validation?

[epananth]

@ViktorHofer yes that is correct.

[epananth]

For stable build test ->https://dnceng.visualstudio.com/internal/_build/results?buildId=803153&view=results

@mmitche please merge this PR for me, I do not have access to merge this one.

[ViktorHofer]

@epananth my question was if we can/should move the whole "Validate Build Assets" stage out of the build.

[mmitche]

@epananth my question was if we can/should move the whole "Validate Build Assets" stage out of the build.

@epananth I think we can for v3 publishing. If none of the SDL, etc. validations are enabled and v3 is enabled, then I don't think this stage doesn't have any real purpose. It used to verify that the default channel was available, but in v3 this is not a relevant concern.

Does that sound right to you?

[epananth]

Thanks @mmitche! I created a issue to safely remove this stage for V3.

[jkoritzinsky]

@epananth is there a plan to move master to publishing v3 as well?

[epananth]

@jkoritzinsky you can just merge release/5.0-rc2 to master then it should pick up the V3 changes.

[jkoritzinsky]

We don't merge release branches back to master in dotnet/runtime. We exclusively use the dual-checkin model.

If this change should work as written against master, we can use the backport GitHub action to port it to master.

[epananth]

oh okay, good to know.

The changes should work in master. Like discussed, I will run my changes against master and back port it to master.