Artifacts in Azure Pipelines
Azure Pipelines | TFS 2018 | TFS 2017 | TFS 2015.3 and newer | TFS 2015 RTM (see Q&A)
In Microsoft Team Foundation Server (TFS) 2018 and previous versions, build and release pipelines are called definitions, service connections are called service endpoints, stages are called environments, and jobs are called phases.
You can publish and consume many different types of packages and artifacts with Azure Pipelines. Your continuous integration (CI)/continuous deployment (CD) pipeline can publish specific package types to their respective package repositories (NuGet, npm, Python, etc.), or you can leverage Build artifacts/Pipeline Artifacts (Preview) to help store build outputs and intermediate files between build steps where they can be added onto, built, tested, or even deployed.
Supported artifact types
Below you will find a table of supported artifact types in Azure Pipelines.
|Supported artifact types||Description|
|Build artifacts||Build artifacts are the files that you want your build to produce. Build artifacts can be nearly anything your team needs to test or deploy your app. For example, you've got a .DLL and .EXE executable files and .PDB symbols file of a C# or C++ .NET Windows app.|
|Pipeline Artifacts (Preview)||You can use Pipelines Artifacts to help store build outputs and move intermediate files between jobs in your pipeline. Pipeline Artifacts are tied to the pipeline that they are created in and can be used within the pipeline and downloaded from the build as long as the build is retained. Pipelines Artifacts are the new generation of Build artifacts, they leverage existing services to dramatically reduce the time it takes to store outputs in your pipelines.|
|Maven||You can publish Maven artifacts to Azure Artifacts feeds or Maven repositories.|
|npm||You can publish npm packages to Azure Artifacts or npm registries.|
|NuGet||You can publish NuGet packages to Azure Artifacts, other NuGet services (like NuGet.org), or interal NuGet repositories.|
|PyPI||You can publish Python packages to Azure Artifacts or PyPI repositories.|
|Symbols||Symbol files contain debugging information for compiled executables. You can publish symbols to symbol servers, which enable debuggers to automatically retrieve the correct symbol files without knowing specific product, package, or build information.|
|Universal||Universal Packages store one or more files together in a single unit that has a name and version. Unlike Pipeline Artifacts that reside in the pipeline, Universal Packages reside within a feed in Azure Artifacts.|
How do I publish and consume artifacts?