AzureDevOps artifact feed has reached free tier limit
See original GitHub issueError: An unexpected error occurred while trying to push the package with VstsNuGetPush.exe. Exit code(1) and error(Error:
Microsoft.VisualStudio.Services.Content.Common.ArtifactBillingException: Artifact cannot be uploaded because max quantity has been exceeded or the payment instrument is invalid. https://aka.ms/artbilling for details.
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<HandleResponseAsync>d__53.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__51.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at VstsNuGetPush.PackageAdder.AddPackageToFeed(FeedCoordinates feed, BlobIdentifierWithBlocks blobId, Boolean muted)
at VstsNuGetPush.VstsNuGetPushBlobStoreOperation.AddPackageToFeed(BlobIdentifierWithBlocks blobId, Boolean muted)
at VstsNuGetPush.VstsNuGetPushBlobStoreOperation.Execute()
at VstsNuGetPush.VstsNuGetPushCommand.MainCore(ILogger logger)
at VstsNuGetPush.VstsNuGetPushCommand.Main())
Packages failed to publish
Issue Analytics
- State:
- Created 3 years ago
- Comments:21 (13 by maintainers)
Top Results From Across the Web
View Artifacts storage consumption - Azure DevOps
The free-tier plan provides a storage capacity of two Gibibytes (GiB) to store various package types. If you exceed the storage limit, ...
Read more >Azure artifact cannot be uploaded because max quantity ...
Azure Artifacts includes a free usage tier of 2 GB. ... Once the maximum usage limit is reached, you can no longer upload...
Read more >Artefact usage seems incorrect and now I'm blocked
I realized then that there is a 2 GB free tier and after that you pay per GB. So I reckon we must...
Read more >Azure Artifacts vs Build Artifacts vs Pipeline Artifacts
You have a free grant of 2 Gb for each organization, but once you reach the maximum storage limit, you can no longer...
Read more >Microsoft's Azure DevOps: An Unsatisfying Adventure
On top of that Microsoft has some odd pricing in that they limit your self hosted pipeline concurrency to 1 unless you pay...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like the 3.2.16 release went well to both the DevOps feed and nuget.org, so we should close this issue now.
Since I downloaded all versions of all packages to take a backup of them, the retention settings won’t delete anything until in 30 days. I’ve created a separate Azure Subscription and configured billing for our DevOps organization. Now there’s no spending limit on Azure Artifacts, so we should be able to deploy pre-releases to the feed again.
I’ll watch this in the coming months. If we’re able to get down to under 2GBs again, I can remove the billing subscription from the DevOps Organization.
I’ve modified the release pipeline to use the Azure Artifacts feed called “fluentmigrator” again instead of the GitHubPackages configuration. I can remove that service connection, since it didn’t work anyway.
We can close this issue as soon as we’ve verified that the modifications on the release pipeline has been reverted and it works as intended again. And we should probably reorganize the FluentMigrator.Console NuGet package, so that it’s possible to install DB provider packages as needed instead of bundling all provider DLLs with every version of that package.