Azure DevOps nuget artifact delay

5
votes

We have a dotNET pipeline set up as a class library that the pipeline builds into a nupkg file and pushes to our Azure DevOps hosted artifact library. This works fine, and if we navigate to the Artifacts tab immediately after the build completes we can see the new package version as expected.

However, what we are seeing is anywhere from a 0 to 30-minute delay before we can consume said package using nuget. Have tried consuming it both on my local development machine and also as part of another pipeline in Azure DevOps and neither of them can access the new package version.

The trick so far seems to be, wait for the nuget package to build, then wait 30 minutes to use it.

Has anybody else experienced this delay? Is there some eventual consistency happening between the Azure DevOps UI and its nuget server?

1
.netazurenugetdelaydevops

1 Answers

5
votes

This is normal, that is how it works.

When you push a nuget to a repository (Artifacts) in your scenario a lot of things are happening behind the scenes. Some of them would be:

  1. Version validation
  2. Virus checks
  3. Package indexing for searching

This processes usually take from a couple of minutes to half an hour depending on the load of the nuget server. This is the reason your nuget is not immediately available.

For more info you can read the microsoft documentation: https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package