Azure-pipelines-tasks: Nuget push to external nuget server using apikey no longer working

[cory-nmdp]

The Nuget V2 task to push packages to an external Nuget server endpoint using apikey connection is no longer working and returning the following errors:

2017-09-20T16:24:22.7643802Z ##[warning]Can\'t find loc string for key: Error_ApiKeyNotSupported
2017-09-20T16:24:22.7643802Z ##[error]Error: Error_ApiKeyNotSupported

[Zuul86]

Is there any way to use version 2.0.6? It was working in that. Same issue here.

[chrish619]

Seems to have been caused by #5208
Possibly: https://github.com/Microsoft/vsts-tasks/pull/5208/files#diff-a71b45ee54093d79865072cd1f147790 ?

[Zuul86]

To get around this issue I just used Custom and used push as the command and arguments. That way it bypasses that issue.

[PalleDue]

Nuget.exe cannot use wild cards. Instead of using custom I used this inline powershell script:

Write-Host "Looking in path $Env:BUILD_SOURCESDIRECTORY"
$files = Get-ChildItem -Path "$Env:BUILD_SOURCESDIRECTORY" -Recurse -Include *.nupkg -Name
$apikey = <apikey>
$nugetsource = <nugetsource>
foreach ($f in $files)
{
    Write-Host $f
    &nuget.exe push $f $apikey -Source $nugetsource
    exit 0
}
exit 1

Obviously this only pushes the first package it encounters. Please modify to your own needs.

[kyleherzog]

Same issue here. I switched to use Custom with the following argument as a workaround for now.

push $(System.DefaultWorkingDirectory)/$(Release.DefinitionName)/drop/Release/** -ApiKey $(NuGet.ApiKey) -Source $(NuGet.Source)

[tkcrown]

Same issue here. Any fix plan? Thanks

[tuyen-vuduc]

+1 here.

[SergeBerwert]

+1

[jonkeda]

+1

[Iapmes]

+1

[daanl]

+1

[antonio-neto-basecone]

+1

[cucamacuca]

+1

[demetrioalvesnl]

+1

[Iapmes]

Easiest work-around for me: Revert back temporarily to using the deprecated NuGet publisher with a generic endpoint. (May require changes to minimatch patterns.)

[xavierdecoster]

For any MyGet users affected by this VSTS change: your MyGet username and MyGet scoped access token (API key) can also be used for Basic Authentication.

Note: don't use the _Primary API Key_, but create a _scoped_ key instead. Primary API key won't work for Basic Auth.

You can update the NuGet Service Connection in your Team Project to use Basic Authentication, and leverage your MyGet scoped API key and MyGet username as basic auth credentials.

We updated the MyGet docs to reflect this:
https://docs.myget.org/docs/reference/vsts-integration#Add_a_NuGet_Service_Connection_to_your_MyGet_feeds

[pedro-resende-1981]

+1

[jiraf]

+1

[advdberg]

+1

[fvelasco1]

+1

[jochenvangasse]

+1

[SanderSiep]

+2

[alesebi91]

+1

[cvvvlad]

+1

[mikehowey1]

Auto updates without rollback.....going to be the death of the platform real quick.

[infin8x]

Thanks for reporting. We're determining the root cause of this issue now and will share more details here soon.

[wyrdfish]

We also used the deprecated push command also with a generic service endpoint.
maybe allowing the task version selector to be explicit not just major version would help in these instances.

[infin8x]

This is now being tracked as an incident: https://blogs.msdn.microsoft.com/vsoservice/?p=15005

[scottkoland]

+1

[baskint]

👍

[felipeOliveira]

+1

[Schenz]

+1

[infin8x]

The fix is now out to all but one of the remaining deployment rings. The majority of users should be unblocked now; the failure rate is down to ~6%. The current ETA for completing this on the final deployment ring is 22:00 UTC. We will provide another update in 2 hours or less at https://blogs.msdn.microsoft.com/vsoservice/?p=15005

[keithrob]

@chrish619 ,
The PR you linked to wasn't the root cause. The root cause is this.
Keith

[chrish619]

@keithrob: Fair enough, I did mention it was a _possible_ cause;
Also, a null coalescing truthy, in this method, e.g.

function test(param?:boolean){
  param = param || true; // ?
  return param;
}

Will always evaluate to true..