Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Packages not appearing in Proget feed
-
Hi,
I am trying to push a Nupkg file from TFS 2018 to Proget, using the Nuget push comand.However, even though the build runs successfully, I see nothing in Proget?
I can send screenshots of the configuration.
Thanks
Product: ProGet
Version: 5.0.8
-
Check the logs of your TFS build; it's most likely that it's not being pushed, or there is some sort of error (even though it might not be logged as an error), such as unauthorized, etc.
If there is an error, you can find ProGet's error logs under Admin > Error logs. If an unexpected error (invalid package, etc) occurred during the push, then it would be logged there.
-
Ok so I've done some more testing, but from a command line. This is what I get:
There is the general API key in settings and also the Nuget API key.
nuget push SampleCode2.1.0.0.0.nupkg 28055 -Source http://10.0.0.211:81/feeds/TestSitePackages/
This works with the output:
Pushing SampleCode2.1.0.0.0.nupkg to 'http://10.0.0.211:81/feeds/GurdipTestSitePackages/'...
PUT http://10.0.0.211:81/feeds/GurdipTestSitePackages/
OK http://10.0.0.211:81/feeds/GurdipTestSitePackages/ 277ms
Your package was pushed.But I dont see anything in the feed itself at the url?
-
It looks like you're using the wrong URL. Make sure to use the "API endpoint url", shown on the feed page, as well as the package page.
http://10.0.0.211:81/nuget/GurdipTestSitePackages/
vs
-
Hmm, with the API url, I get 403.
I am using the API key that is set on the feed in properties.
-
The API key is a bit confusing, so please don't use it. In v5, it's no longer supported anyways.
You can authenticate with name:password as an api key instead.
-
So in the case of my usernane and pwd being Admin, Admin:Admin ?
-
Ok so I tried:
nuget push SampleCode2.1.0.0.0.nupkg Admin:Admin
-Source http://10.0.0.211:81/nuget/TestSitePackages/But vstill get a 403.
-
Ok got this working by removing the api key in the feed properties, thanks!