You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/understand-package-management/includes/9-publish-packages.md
+10-31Lines changed: 10 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,46 +4,25 @@ Discussed previously was guidance to find components that can be isolated into d
4
4
5
5
These components need to be managed and packaged. After that, they can be published to a feed, allowing others to consume the packages and use the components it contains.
6
6
7
-
## Creating a feed
7
+
## Create a feed
8
8
9
-
The first step is to create a feed where the packages can be stored. In Azure Artifacts, you can create multiple feeds, which are always private.
9
+
The first step is to create a feed where your packages will be stored. Azure Artifacts allows you to create multiple feeds as needed.
10
10
11
-
During creation, you can specify the name, visibility and prepopulate the default public upstream sources for NuGet, npm, and Python packages.
11
+
When creating a feed, you can specify the name, set the visibility, and choose whether to include packages from common public sources such as NuGet.org and npmjs.com.
12
12
13
13
## What are feeds in Azure Artifacts?
14
14
15
-
Most package management systems provide endpoints where you can request packages to install in your applications. Those endpoints are called feeds.
15
+
In Azure Artifacts, you can create multiple feeds within your projects. Feeds can be scoped to your project or made available across your entire organization.
16
16
17
-
In Azure Artifacts, you can have multiple feeds in your projects, and you can make them available to only users authorized in your project or for your entire organization.
17
+
Feeds can store packages of different types such as npm, NuGet, Maven, Python, Cargo, and Universal Packages. Each feed can include one or more upstream sources and has its own configurable security settings.
18
18
19
-
Each feed can contain any packages, even mixed types, but it's recommended that you create one feed per type you want to support in your organization, this way, it's clear what the feed contains.
19
+
Azure Artifacts enables developers to store, manage, and share their packages while maintaining access control. Developers can control how packages are shared, restricting access to specific users, teams, or organizations, or making packages publicly available.
20
+
21
+
## Publish packages to a feed
20
22
21
-
Each feed can contain one or more upstream and can manage its security.
23
+
Azure Artifacts supports a wide range of package types and technologies. Each package manager has a different workflow for authenticating with Azure Artifacts and publishing packages to a feed.
22
24
23
-
## Controlling access
24
-
25
-
The Azure Artifacts feed you created is always private and not available publically.
26
-
27
-
You need access to it by authenticating to Azure Artifacts with an account with access to Azure DevOps and a team project.
28
-
29
-
By default, a feed will be available to all registered users in Azure DevOps.
30
-
31
-
You can select it to be visible only to the team project where the feed is created.
32
-
33
-
Whichever option is chosen, you can change the permissions for a feed from the settings dialog.
34
-
35
-
## Push packages to a feed
36
-
37
-
Once you've authenticated to Azure DevOps, you can pull and push packages to the package feed, provided you have permission to do so.
38
-
39
-
Pushing packages is done with the tooling for the package manager. Each of the package managers and tooling has a different syntax for pushing.
40
-
41
-
To manually push a NuGet package, you would use the `NuGet.exe` command-line tool. For a package called `MyDemoPackage,` the command would resemble:
To find the right workflow for your technology, sign in to your Azure DevOps organization, navigate to **Artifacts**, then select **Connect to feed**. From the left panel, choose the package type you're working with and follow the **Project setup** instructions. See [Get started with Azure Artifacts](/azure/devops/artifacts/start-using-azure-artifacts#get-started) for more details.
0 commit comments