3 ms·
In Azure DevOps pipelines there's a fun issue where if you're pulling a dependency from nuget.org it gets pulled very quickly, but pulling from your own artifac
by HideousKojima 3y ago
In Azure DevOps pipelines there's a fun issue where if you're pulling a dependency from nuget.org it gets pulled very quickly, but pulling from your own artifact repositories hosted in the very same Azure DevOps instance take 40-80 seconds. I'm not the one paying the extra bills when my builds take 5 to 6 times longer than they should but it's still frustrating.
And Microsoft has effectively zero incentive to fix this because it still technically works and they get to charge my employer for all that extra build agent time. Here's a few examples of people reporting similar issues and getting zero help:
https://developercommunity.visualstudio.com/t/devops-build-pipeline-nuget-restore-very-slow-on-s/632309 https://developercommunity.visualstudio.com/t/devops-build-p...
https://developercommunity.visualstudio.com/t/nuget-restore-takes-25-of-the-time-of-my-build/1027210 https://developercommunity.visualstudio.com/t/nuget-restore-...
https://developercommunity.visualstudio.com/t/slow-performance-when-downloading-from-private-nug/476627 https://developercommunity.visualstudio.com/t/slow-performan...
- easton 3y agoMicrosoft hosted agents aren’t charged by the minute on ADO, IIRC. You pay for a certain number of parallel agents per month. Unless you’re booting build servers on demand on your infra, you aren’t paying more for more minutes. Just waiting :( (Unlike GitHub, where they do charge per minute.)
- namtab00 3y agodo you know if ADO has any caching mechanisms for pipelines doing builds?
- HideousKojima 3y agoThe issue in this case isn't caching, even if I'm not actually pulling any packages from our private nuget repo simply having that repo listed in the project's nuget.config file is enough to cause the issue.