Restoring from private azure devops feeds is flaky
See original GitHub issueWe have been seeing multiple issues when restoring from azure devops private feeds.
These errors usually manifest in 401/403/404 errors when attempting to restore packages, and are caused by a mix of bugs in NuGet / The credential provider / MSBuild.
While we have some more information as to when the issues will be fixed, the azure artifacts team recommended a wokaround:
- Clear the
nuget http-cache
before attempting to restore any packages from these feeds - Set the following environment variables:" NUGET_PLUGIN_HANDSHAKE_TIMEOUT_IN_SECONDS=20 NUGET_PLUGIN_REQUEST_TIMEOUT_IN_SECONDS=20
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Flaky "dotnet restore" fails randomly in Azure Pipeline
It links to a feed in Azure Devops (Artifacts). Our feed includes the sources that the errors say are missing. It's always warning...
Read more >Manage flaky tests - Azure Pipelines
A flaky test is a test that provides different outcomes, such as pass or fail, even when there are no changes in the...
Read more >Solving Long, flaky testing with Azure DevOps - Tsuyoshi Ushio
The first try ... Unfortunately, the task has been canceled. The reason is it took over 30 min. By default, Hosted agent will...
Read more >Azure DevOps and Telerik NuGet Packages
How does the pipeline restore a package that is only in a private feed? This is where a NuGet config file comes into...
Read more >dotnet restore" fails randomly in Azure Pipeline
Coding example for the question Flaky "dotnet restore" fails randomly in Azure Pipeline.
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
The NuGet changes will be available in the 3.1.200 SDK, we should update Arcade (and dependent repos) to that version when it’s released to see if that solves the flakiness.
I think this might just been an agent network problem, looking at the logs for that failed build leg, I see stuff such as:
Which means it had problems restoring from even the sleet feeds, and not just with the artifacts feeds.