Skip to content

Latest commit

 

History

History
45 lines (31 loc) · 1.68 KB

limits.md

File metadata and controls

45 lines (31 loc) · 1.68 KB
Raw
title description ms.service ms.topic ms.date monikerRange
Size and count limits
Package count and size limits in Azure Artifacts
azure-devops-artifacts
conceptual
02/25/2022
<= azure-devops

Package sizes and count limits

[!INCLUDE version-lt-eq-azure-devops]

Azure Artifacts is a highly scalable package management solution that enables developers to create, host, and share different types of packages. In this article, we will cover the size and count limits that developers should be aware of when using Azure Artifacts. Some of these limits are imposed by the client tools that Azure Artifacts integrates with (example nuget.exe).

Count limits

  • 5000 versions per package ID.
  • Unlimited package IDs per feed.
  • 20 upstreams per package type per feed.

Note

You can use retention policies to automatically delete older package versions.

Size limits

  • NuGet packages: limited to 500 MB per file.

  • Npm packages: limited to 500 MB per file.

  • Maven packages: limited to 500 MB per file.

  • Python packages: limited to 500 MB per file. ::: moniker range="= azure-devops"

  • Universal Packages: up to 4 TB per file (Recommended for large binary files). ::: moniker-end

Note

Universal Packages are only available in Azure DevOps Services.

Related articles