Closed quasarea closed 5 years ago
also it is odd how first and last output of Command-line differs:
[09:45:28.306 4876 Verbose]
Command-line v0.1.19:
..\..\..\Build\NuGet\Client\CredentialProvider.Microsoft.exe
-nonInteractive
-uri https://Company.pkgs.visualstudio.com/_packaging/CompanyFeed/nuget/v3/index.json
[09:47:40.704 10724 Verbose]
Command-line v0.1.19:
"M:\CurrentModule\Build\NuGet\Client\CredentialProvider.Microsoft.exe"
-uri https://pkgs.dev.azure.com/Company/_packaging/CompanyFeed/nuget/v3/index.json
-nonInteractive
I think there are a few things getting mixed up here:
It looks like NuGet is trying to use the "old-style" credential provider mechanism with this, the "new-style" credential provider plugin. If you want a standalone instance of the credential provider, I would move it to a folder which is neither the same folder nor a subfolder of the folder that contains nuget.exe, and set the environment variable NUGET_PLUGIN_PATHS to the absolute path (including file name) to CredentialProvider.Microsoft.exe. Alternatively, follow the instructions in the README to install to the central user location
I think the runs which are succeeding are succeeding for a reason unrelated to authentication, such as having all packages not accessible from some source without authentication already cached
I have nuget executable (5.2.0.6090) in same folder that credential provider (0.1.19) is.
I call the same command, using the same user (generic account) across few nodes.
NuGet.Config
I do
before the run. If it's successful I get:
odd bit here is that I migrated Company.pkgs.visualstudio.com to pkgs.dev.azure.com few weeks ago
when failing log is the same as succesful one, but then expands:
Last password here has same front, but different two other bits, while initial password is same