Matt Mitchell
Matt Mitchell
> Let's start over then. Pretend I'm a customer (this happened in real life) and I'm looking for the ci build equivalent of this page https://dotnet.microsoft.com/download/dotnet/5.0. Am I now forced...
> I'm not sure why this is complicated... It's complicated because there is a ton of subtlety that is hidden away when we have a coherent build. Implicitly installer **is**...
> I don't think coherence is a problem One more thing. Coherence may be a problem depending on what the expectations are for someone using this site. When they use...
From the context of someone using the installer, they would see the same behavior, So if this is really just about making explicit the links of what is included in...
> And I still prefer SDK team not owning this feature. The central engineering team should have better access like darc and aka.ms/bar to build it. And they are better...
> How are the links generated today? Any repo may publish various blobs (e.g. Sdk/5.0.100-rc.1.1234.5/dotnet-sdk-5.0.100.rc.1.1234.5-win-x64.zip). These are published to a location based on what channel the build is assigned to...
https://dev.azure.com/dnceng/internal/_build/results?buildId=2483907&view=results
I think this is okay, but I think it would be good to verify source builds. Can you push a branch to the AzDO dotnet-dotnet repo with those changes to...
@sharwell @tmat Can you add a description for why this change is necessary? What is the root purpose?
@pavel-purma How did we figure this out in the old pipeline?