What are feeds?
TFS 2017
Artifacts Feeds are organizational constructs that allow you to store, manage, and group your packages and control who to share it with. Feeds are not package-type dependent. You can store all the following package types in a single feed: npm, NuGet, Maven, Python, and Universal packages.
Project-scoped vs Organization-scoped feeds
Previously, all feeds were scoped to an organization, they could be viewed and accessed in the Azure Artifacts hub from any project within an organization. With the introduction of public feeds, we also introduced project-scoped feeds. This type of feed can only be accessed from within the hosting project.
Only project-scoped feeds can be made public. You can learn more about public feeds later in this article. See Feeds visibility to understand the differences between project-scoped and organization-scoped feeds.
Note
To access a feed in a different organization, a user must be given access to the project hosting that feed.
Public feeds
Public feeds are used to share your packages publicly with anyone on the Internet. Users won't have to be a member of your organization or your enterprise. They can access the packages even if they don't have an Azure DevOps account.
Public feeds are project-scoped feeds and it will inherit the visibility settings of the hosting project.
There some important things to note regarding public feeds:
- Public feeds can only be created inside of public projects.
- Public feeds aren't intended as a replacement for existing package management platforms (NuGet.org, npmjs.com, etc.).
- Public feeds cannot have upstream sources.
- Public users cannot currently download universal packages. All other package types are supported for public access.
Create public feeds
Public feeds are project-scoped feeds in a public project.
Select Artifacts.
Select Create Feed.
Give your feed a Name, and then select Project for your feed's scope.
Select Create when you are done.