azure devops build pipeline private nuget feed

A special consideration should be done to the last parameter in Figure 4 used to decide if this service connection can be used by any pipeline. Now you should select Nuget Connection type:įigure 3: Choose Nuget as Service Connection TypeĪt this point you must specify all the information to connect to the feed you need, you should add the same NuGet feed address contained in nfig, give it a name and specify an access token. In such a situation you need to proceed in a different route, first of all you need to go on Team Project settings to add a Service Connection that points to nuget feed.įigure 2: Go to Team Project settings to add a Service Connection A different scenario happens when you want to use nuget against an authenticated feed that resides somewhere else (different organization, MyGet or other provider). The aforementioned NugetAuthenticate task can be used as is if you need to authenticate to feeds that belong to the very same organization. Once I’ve added it subsequent commandline nuget.exe commands work like a charm without any hiccup.įigure 1: Nuget Restore correctly restored everything without any problem

WorkingDirectory: $(Build.SourcesDirectory)įilePath: '$(Build.SourcesDirectory)/Build.ps1' arguments: -skipPackageInstallation $ falseĪs you can see in line 9 I simply added a NuGetAuthenticate task that does all the dirty work for me. task: 2 displayName: 'Full Powershell Build' inputs: Version: 3.1.201 performMultiLevelLookup: true - task: 0 Task is called and if the feed is on the very same organization you can simply add as shown in following snippet of a YAML pipeline.

This is annoying and happens with every nuget feed that needs authentication but the solution is really simple because you have a special task that helps authenticating to Feed in the same organization or in different organization or in any other NuGet server that requires login. Remember that this problem does not happen if you use standard NuGet task, but happens usually when you manual call NugetExe in PowerShell or other scripts. This happens because the feed is authenticated, nuget.exe is trying to open the typical popup window to allow for login, but since the build is running without a user interface, the whole process hang. User sign-in required in a pop-up authentication window. Using the ADAL UI flow for uri /nuget/v3/index.json.

Azure devops build pipeline private nuget feed