-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REGRESSION]: #20854
Comments
Sometime the restore reach to the end successfully, other time fail with the same error message. I'm forcing the pipeline to use the old version like this (to fix the issue temporally):
But something very strange is happening with the version 2.252.1 |
Hi @coby Allred |
Thanks @censurados - was having the exact same issue and changing to this version worked for me too |
We are getting the same error message |
had same issue. in my case adding of the option:
solved the issue in my pipelines. Please note the default option is set to 'Detailed': |
Hi @censurados Do you have a step-by-step tutorial to force the version downgrade? I'm a beginner with pipeline/nuget |
Just a heads up, you tagged the wrong person. |
New issue checklist
Task name
NuGetCommand@2
Breaking task version
2.252.1
Last working task version
2.238.1
Regression Description
When I'm trying to restore the packages and I only see warning NU1608 before the fail message . Adding the NU1608 to the build props NoWarn node, now the task reach the end but still fail with the message
2025-02-13T19:43:50.8460630Z ##[error]The nuget command failed with exit code(null) and error()
2025-02-13T19:43:50.8472878Z ##[error]Packages failed to restore
2025-02-13T19:43:50.8477997Z ##[section]Finishing: Restore NuGet Packages *** with FIM Shared Packages
Can you help me please, right now I have all the deploys stopped. Thanks
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
windows-2022
Relevant log output
Full task logs with system.debug enabled
UNSUCCESSFUL RUN
SUCCESSFUL RUN
Repro steps
The text was updated successfully, but these errors were encountered: