Skip to content

Migrate static sleet feed into public Azure DevOps artifact feed #6952

@miniksa

Description

@miniksa

Per @jevansaks, Azure DevOps apparently made artifact feeds a thing that can be made public (and not just "authenticated users.")

The only reason we were using a Sleet feed in an Azure Blob Storage bucket for our NuGet packages was because of this limitation.

This work item represents decommissioning future use of the sleet feed in the bucket, creating one of those public artifact feeds on the ms instance of Azure DevOps that we already use for build, and publishing our dependent artifact pages there.

This is what we think needs to move:

  • Microsoft.UI.XAML package
  • vcpkg for cpprestsdk
  • vcpkg for telnetpp
  • Terminal theme helpers

I also expect this to help us enable doing PGO the same way that https://github.com/microsoft/microsoft-ui-xaml does from @bartekk8's work on that there.

Metadata

Metadata

Assignees

Labels

Area-BuildIssues pertaining to the build system, CI, infrastructure, metaIssue-TaskIt's a feature request, but it doesn't really need a major design.Needs-Tag-FixDoesn't match tag requirementsProduct-MetaThe product is the management of the products.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions