arcade
arcade copied to clipboard
dotnet
Provide external partners access to pre-release packages
We need a way to provide enterprise source-build partners access to our product packages pre-release. We currently provide pre-release source-build access to these partners so that they can build and test in order to co-release .NET for both servicing and major releases. These partners need access to the product packages for E2E testing scenarios (not all components are source-built - e.g. workloads).
In talking with @mmitche, providing access to the package feeds is not plausible. He suggested we could modify our builds to create a package archive artifact that we can then share.
I wonder if this is another example of things we need/should do in support of shipping .NET 7?
This does seem like something that would be involved in supporting the shipping of .NET 7
6.0 and 7.0 currently use the same staging pipeline, so any improvements would apply to 6.0.
@mmitche, @adiaaida - is there a plan on when this could be fixed? This is something that continue to be a tax for the source-build team to pay.
Yea, I'd be sure and bring this up as something we really need to do now that we're about to enter planning @MichaelSimons
@MichaelSimons We have a way to provide a unified pre-release package feed in dnceng/internal for internal partners. I think we can duplicate that model into the early access AzDO instance. Can you create a feed for this? Call it: dotnet6-early-access? I can manually push packages when we're signed off for a release. At some point we should integrate this into the release pipeline
@mmitche - Great suggestion - I created dotnet6-early-access (internal link). Let me know when you push the packages and I can ask our partners to verify their e2e by utilizing this feed.