Skip to content
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

Open
5 of 7 tasks
censurados opened this issue Feb 13, 2025 · 7 comments
Open
5 of 7 tasks

[REGRESSION]: #20854

censurados opened this issue Feb 13, 2025 · 7 comments
Labels
Area: Artifacts bug regression This used to work, but a change in the service/tasks broke it. triage

Comments

@censurados
Copy link

censurados commented Feb 13, 2025

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)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

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

2025-02-13T19:41:06.2934470Z ##[section]Starting: Restore NuGet Packages *** with FIM Shared Packages
2025-02-13T19:41:06.2949481Z ==============================================================================
2025-02-13T19:41:06.2949785Z Task         : NuGet
2025-02-13T19:41:06.2949973Z Description  : Restore, pack, or push NuGet packages, or run a NuGet command. Supports NuGet.org and authenticated feeds like Azure Artifacts and MyGet. Uses NuGet.exe and works with .NET Framework apps. For .NET Core and .NET Standard apps, use the .NET Core task.
2025-02-13T19:41:06.2950388Z Version      : 2.252.1
2025-02-13T19:41:06.2950572Z Author       : Microsoft Corporation
2025-02-13T19:41:06.2950794Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/package/nuget
2025-02-13T19:41:06.2951033Z ==============================================================================
2025-02-13T19:41:07.2942605Z [command]C:\Windows\system32\chcp.com 65001
2025-02-13T19:41:07.2962759Z Active code page: 65001
2025-02-13T19:41:08.5388842Z Detected NuGet version 6.12.2.1 / 6.12.2+c097388782da305f47c395f90bea2d7c83909b6d.c097388782da305f47c395f90bea2d7c83909b6d
2025-02-13T19:41:08.6041760Z [command]C:\hostedtoolcache\windows\NuGet\6.12.2\x64\nuget.exe sources Add ***NonInteractive ***Name FimSharedPackages ***Source https://pkgs.dev.azure.com/agg***spear***fim/FIM%20Shared%20Packages/_packaging/FimSharedPackages/nuget/v3/index.json ***ConfigFile D:\a\1\Nuget\tempNuGet_8497.config
2025-02-13T19:41:12.0953949Z Package source with Name: FimSharedPackages added successfully.
2025-02-13T19:41:12.0993129Z [command]C:\hostedtoolcache\windows\NuGet\6.12.2\x64\nuget.exe sources Add ***NonInteractive ***Name NuGetOrg ***Source https://api.nuget.org/v3/index.json ***ConfigFile D:\a\1\Nuget\tempNuGet_8497.config
2025-02-13T19:41:12.9609893Z Package source with Name: NuGetOrg added successfully.
2025-02-13T19:41:12.9650465Z [command]C:\hostedtoolcache\windows\NuGet\6.12.2\x64\nuget.exe restore D:\a\1\s\Src\FundManager.sln ***Verbosity Detailed ***NonInteractive ***ConfigFile D:\a\1\Nuget\tempNuGet_8497.config
2025-02-13T19:43:50.0663777Z NuGet Version: 6.12.2.1
2025-02-13T19:43:50.0665627Z MSBuild auto***detection: using msbuild version '17.12.12.57101' from 'C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\bin'. Use option ***MSBuildVersion to force nuget to use a specific version of MSBuild.
2025-02-13T19:43:50.0667123Z MSBuild P2P timeout [ms]: 588000
2025-02-13T19:43:50.0668907Z C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\bin\msbuild.exe "C:\Users\VssAdministrator\AppData\Local\Temp\NuGetScratch\emxatvt0.gmm.nugetinputs.targets" /t:GenerateRestoreGraphFile /nologo /nr:false /v:q /p:NuGetPropsFile="C:\Users\VssAdministrator\AppData\Local\Temp\NuGetScratch\kei5yzjq.wnb.nugetrestore.props" /p:NuGetRestoreTargets="C:\Users\VssAdministrator\AppData\Local\Temp\NuGetScratch\xdbaqfhv.zcm.nugetrestore.targets" /p:RestoreUseCustomAfterTargets="True" /p:DisableCheckingDuplicateNuGetItems="True" /p:RestoreTaskAssemblyFile="C:\hostedtoolcache\windows\NuGet\6.12.2\x64\nuget.exe" /p:RestoreSolutionDirectory="D:\a\1\s\Src\\" /p:RestoreConfigFile="D:\a\1\Nuget\tempNuGet_8497.config" /p:SolutionDir="D:\a\1\s\Src\\" /p:SolutionName="FundManager"
2025-02-13T19:43:50.0670028Z 
2025-02-13T19:43:50.0671006Z Running restore with 2 concurrent jobs.
...
2025-02-13T19:43:50.8198976Z     307 package(s) to D:\a\1\s\Src\Reporting\FundManager.Reporting.Interfaces\FundManager.Reporting.Interfaces.csproj
2025-02-13T19:43:50.8199658Z     408 package(s) to D:\a\1\s\Src\Security\FundManager.Security.Application\FundManager.Security.Application.csproj
2025-02-13T19:43:50.8200389Z     16 package(s) to D:\a\1\s\Src\Reporting\FundManager.Reporting.Infrastructure.Tests\FundManager.Reporting.Infrastructure.Tests.csproj
2025-02-13T19:43:50.8201199Z     311 package(s) to D:\a\1\s\Src\Reporting\FundManager.Reporting.Domain\FundManager.Reporting.Domain.csproj
2025-02-13T19:43:50.8201851Z     461 package(s) to D:\a\1\s\Src\Reporting\FundManager.Reporting.Application\FundManager.Reporting.Application.csproj
2025-02-13T19:43:50.8202492Z     16 package(s) to D:\a\1\s\Src\Reporting\FundManager.Reporting.Application.Tests\FundManager.Reporting.Application.Tests.csproj
2025-02-13T19:43:50.8203303Z     1 package(s) to D:\a\1\s\Src\Reporting\FundManager.Reporting.Infrastructure\FundManager.Reporting.Infrastructure.csproj
2025-02-13T19:43:50.8203935Z     415 package(s) to D:\a\1\s\Src\MarketData\FundManager.MarketData.Services\FundManager.MarketData.Services.csproj
2025-02-13T19:43:50.8204565Z     16 package(s) to D:\a\1\s\Src\MarketData\FundManager.MarketData.Services.Tests\FundManager.MarketData.Services.Tests.csproj
2025-02-13T19:43:50.8205226Z     430 package(s) to D:\a\1\s\Src\MarketData\FundManager.MarketData.Persistance\FundManager.MarketData.Persistence.csproj
2025-02-13T19:43:50.8205858Z     415 package(s) to D:\a\1\s\Src\MarketData\FundManager.MarketData.Interfaces\FundManager.MarketData.Interfaces.csproj
2025-02-13T19:43:50.8206495Z     1 package(s) to D:\a\1\s\Src\MarketData\FundManager.MarketData.Infrastructure\FundManager.MarketData.Infrastructure.csproj
2025-02-13T19:43:50.8207147Z     16 package(s) to D:\a\1\s\Src\MarketData\FundManager.MarketData.Infrastructure.Tests\FundManager.MarketData.Infrastructure.Tests.csproj
2025-02-13T19:43:50.8207783Z     311 package(s) to D:\a\1\s\Src\MarketData\FundManager.MarketData.Domain\FundManager.MarketData.Domain.csproj
2025-02-13T19:43:50.8208403Z     405 package(s) to D:\a\1\s\Src\MarketData\FundManager.MarketData.Application\FundManager.MarketData.Application.csproj
2025-02-13T19:43:50.8209040Z     16 package(s) to D:\a\1\s\Src\MarketData\FundManager.MarketData.Application.Tests\FundManager.MarketData.Application.Tests.csproj
2025-02-13T19:43:50.8209664Z     356 package(s) to D:\a\1\s\Src\Fund\FundManager.Fund.Services\FundManager.Fund.Services.csproj
2025-02-13T19:43:50.8210264Z     449 package(s) to D:\a\1\s\Src\Fund\FundManager.Fund.Services.Tests\FundManager.Fund.Services.Tests.csproj
2025-02-13T19:43:50.8210972Z     438 package(s) to D:\a\1\s\Src\Fund\FundManager.Fund.Persistence\FundManager.Fund.Persistence.csproj
2025-02-13T19:43:50.8211562Z     311 package(s) to D:\a\1\s\Src\Fund\FundManager.Fund.Interfaces\FundManager.Fund.Interfaces.csproj
2025-02-13T19:43:50.8212164Z     307 package(s) to D:\a\1\s\Src\Fund\FundManager.Fund.Infrastructure\FundManager.Fund.Infrastructure.csproj
2025-02-13T19:43:50.8212781Z     456 package(s) to D:\a\1\s\Src\Fund\FundManager.Fund.Infrastructure.Tests\FundManager.Fund.Infrastructure.Tests.csproj
2025-02-13T19:43:50.8213388Z     311 package(s) to D:\a\1\s\Src\Fund\FundManager.Fund.Domain\FundManager.Fund.Domain.csproj
2025-02-13T19:43:50.8214421Z     471 package(s) to D:\a\1\s\Src\Fund\FundManager.Fund.Application\FundManager.Fund.Application.csproj
2025-02-13T19:43:50.8215046Z     487 package(s) to D:\a\1\s\Src\Fund\FundManager.Fund.Application.Tests\FundManager.Fund.Application.Tests.csproj
2025-02-13T19:43:50.8216064Z     365 package(s) to D:\a\1\s\Src\Finance\FundManager.Finance.Services\FundManager.Finance.Services.csproj
2025-02-13T19:43:50.8216886Z     451 package(s) to D:\a\1\s\Src\Finance\FundManager.Finance.Services.Tests\FundManager.Finance.Services.Tests.csproj
2025-02-13T19:43:50.8218192Z     338 package(s) to D:\a\1\s\Src\Finance\FundManager.Finance.Persistence\FundManager.Finance.Persistence.csproj
2025-02-13T19:43:50.8218808Z     349 package(s) to D:\a\1\s\Src\Finance\FundManager.Finance.Interfaces\FundManager.Finance.Interfaces.csproj
2025-02-13T19:43:50.8219573Z     335 package(s) to D:\a\1\s\Src\Finance\FundManager.Finance.Infrastructure\FundManager.Finance.Infrastructure.csproj
2025-02-13T19:43:50.8220203Z     449 package(s) to D:\a\1\s\Src\Finance\FundManager.Finance.Infrastructure.Tests\FundManager.Finance.Infrastructure.Tests.csproj
2025-02-13T19:43:50.8220914Z     311 package(s) to D:\a\1\s\Src\Finance\FundManager.Finance.Domain\FundManager.Finance.Domain.csproj
2025-02-13T19:43:50.8221506Z     469 package(s) to D:\a\1\s\Src\Finance\FundManager.Finance.Application\FundManager.Finance.Application.csproj
2025-02-13T19:43:50.8222127Z     465 package(s) to D:\a\1\s\Src\Finance\FundManager.Finance.Application.Tests\FundManager.Finance.Application.Tests.csproj
2025-02-13T19:43:50.8222772Z     396 package(s) to D:\a\1\s\Src\Documentation\FundManager.Documentation.Services\FundManager.Documentation.Services.csproj
2025-02-13T19:43:50.8223400Z     480 package(s) to D:\a\1\s\Src\Documentation\FundManager.Documentation.Services.Tests\FundManager.Documentation.Services.Tests.csproj
2025-02-13T19:43:50.8224159Z     666 package(s) to D:\a\1\s\Src\Presentation\FundManager.Web\FundManager.Web.csproj
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

Full task logs with system.debug enabled

UNSUCCESSFUL RUN
 [REPLACE THIS WITH YOUR INFORMATION] 
SUCCESSFUL RUN
 [REPLACE THIS WITH YOUR INFORMATION] 

Repro steps

@censurados censurados added bug regression This used to work, but a change in the service/tasks broke it. labels Feb 13, 2025
@censurados
Copy link
Author

censurados commented Feb 13, 2025

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):

  • task: [email protected]
    displayName: 'Restore NuGet Packages'
    inputs:
    restoreSolution: '**/...sln'
    feedsToUse: 'select'
    vstsFeed: '...'
    includeNuGetOrg: true

But something very strange is happening with the version 2.252.1

@v-schhabra
Copy link
Contributor

Hi @coby Allred
Could you or your team please check this issue?

@JGKN-Prodo-2024
Copy link

Thanks @censurados - was having the exact same issue and changing to this version worked for me too

@AndyStevenson7
Copy link

AndyStevenson7 commented Feb 18, 2025

We are getting the same error message The nuget command failed with exit code(null) and error() on several DevOps Build pipelines. What seems to work for us is to set the Number of retries if task failed to 1, in Control Options, on the NuGet Restore step. Looks like it fails only on the first attempt to restore packages.

@Bizz-IBE
Copy link

had same issue. in my case adding of the option:

        verbosityRestore: 'Normal'

solved the issue in my pipelines.

Please note the default option is set to 'Detailed':
#verbosityRestore: 'Detailed' # 'Quiet' | 'Normal' | 'Detailed'. Optional. Use when command = restore. Verbosity. Default: Detailed.

@RDK307
Copy link

RDK307 commented Feb 19, 2025

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):

  • task: [email protected]
    displayName: 'Restore NuGet Packages'
    inputs:
    restoreSolution: '**/...sln'
    feedsToUse: 'select'
    vstsFeed: '...'
    includeNuGetOrg: true

But something very strange is happening with the version 2.252.1

Hi @censurados

Do you have a step-by-step tutorial to force the version downgrade? I'm a beginner with pipeline/nuget

@coby
Copy link

coby commented Feb 19, 2025

Hi @coby Allred Could you or your team please check this issue?

Just a heads up, you tagged the wrong person.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Artifacts bug regression This used to work, but a change in the service/tasks broke it. triage
Projects
None yet
Development

No branches or pull requests

7 participants