TFS invalid package feed permission

For a customer, I recently set up an on-premise package feed.

I left everything to default, added the feed to a Nuget Publish task and pressed release.
The release failed!

2017-07-12T13:25:27.0799281Z Detected NuGet version 3.3.0.212 / 3.3.0
2017-07-12T13:25:27.0955503Z SYSTEMVSSCONNECTION exists true
2017-07-12T13:25:27.0955503Z [command]D:\BldSRC\02\_tasks\NuGetPublisher_333b11bd-d341-40d9-afcf-b32d5ce6f25b\0.2.30\node_modules\nuget-task-common\NuGet\3.3.0\NuGet.exe push -NonInteractive D:\BldSRC\02\r3\a\PackagingTest\drop\XXX.XXX.Core.1.0.0.0.nupkg -Source http://tfs.xxx.xxx.local:8080/tfs/DefaultCollection/_packaging/ProdFeed/nuget/v3/index.json -ApiKey VSTS
2017-07-12T13:25:27.8455507Z Response status code does not indicate success: 403 (Forbidden).
2017-07-12T13:25:27.8768017Z ##[error]Error: D:\BldSRC\02\_tasks\NuGetPublisher_333b11bd-d341-40d9-afcf-b32d5ce6f25b\0.2.30\node_modules\nuget-task-common\NuGet\3.3.0\NuGet.exe failed with return code: 1
2017-07-12T13:25:27.8768017Z ##[error]Packages failed to publish
2017-07-12T13:25:27.8768017Z ##[section]Finishing: NuGet Publisher

After checking that the agent performing the release is actually part of the Project Collection Build Service group. Looking at the feed permissions I noticed that the group added to the Contribute is not valid on the premise group.

After changing that to the valid on-premise group everything succeeded

It’s a small thing to overlook and it will probably be fixed soon in an upcoming on-premise update.

Have Fun!

Share

You may also like...

Leave a Reply