Issue with pushing package to Octopus Built-in Feed

Legacy Execution
1

Hello,
I have two jobs in Jenkins, one that builds an .NET API and one that builds 2 WebJobs to be deployed in Azure.
For the first one (API) I’m able to push the package to Octopus Builtin Feed using an API KEY and for the second job I get 403 (Forbidden) with the same API Key on the same Builtin Feed. :frowning:
Am I missing something with the permissions?

Pushing XXX.Account.API.2.0.40.nupkg to ‘http://10.4.0.4/nuget/packages’…
PUT http://X.X.X.X/nuget/packages/
Created http://X.X.X.X/nuget/packages/ 2080ms
Your package was pushed.

Pushing XXX.WebJobs.Cleanup.2.0.19-CleanUp-WJ.nupkg to ‘http://10.4.0.4/nuget/packages’…
PUT http://X.X.X.X/nuget/packages/
Forbidden http://X.X.X.X/nuget/packages/ 448ms
Response status code does not indicate success: 403 (Forbidden).

2

Hi Alex,

Thanks for getting in touch! Generally when you get this specific error (403 forbidden) it means permissions for the package related to the project do not exist.
Does XXX.WebJobs.Cleanup exist in more than one project? You can only upload packages that are across multiple projects if you have permissions for all of those projects.

Let me know what you find.
Vanessa