Artifacts in Azure Pipelines overview

Azure Artifacts enable developers to consume and publish different types of packages to Artifacts feeds and public registries such as NuGet.org and npmjs.com. You can use Azure Artifacts in conjunction with Azure Pipelines to deploy packages, publish build artifacts, or integrate files between your pipeline stages to build, test, or deploy your application.

Supported artifact types

The following table describes supported artifact types in Azure Pipelines.

Supported artifact type Description
Build artifacts The files produced by a build such as .dll, .exe, or .PDB files.
Maven Publish Maven packages to Azure Artifacts feeds or Maven central repository.
npm Publish npm packages to Azure Artifacts feeds or npm registry.
NuGet Publish NuGet packages to Azure Artifacts feeds or NuGet public repository.
PyPI Publish Python packages to Azure Artifacts feeds or PyPI registry.
Universal packages Publish Universal Packages to Azure Artifacts feeds.
Symbols Symbol files contain debugging information about the compiled executables. You can publish symbols to a symbol server in Azure Artifacts to debug your application. Symbol servers enable debuggers to automatically retrieve the correct symbol files without knowing the specific product, package, or build information.

How do I publish and consume artifacts?

Each kind of artifact has a different way of being published and consumed. Some artifacts are specific to particular development tools, such as .NET, Node.js/JavaScript, Python, and Maven. Other artifact types offer more generic file storage, such as pipeline artifacts and Universal Packages.

Next steps