Thanks Justin; we definitely need to improve docs. I just made a change to it now to clarify this better: https://github.com/Inedo/inedo-docs/blob/master/ProGet/feeds/maven.htm

ProGet does not push packages; but you can use a tool like BuildMaster to help build a pipeline for your own nuget packages, and push to different nuget servers along the way.

Just seen that .18 has been release. Tested and working. Ignore above.

UPDATE: this was resolved through our ticket-based support. The underlying issue was "Unable to reach credential server" s3, and it was related to how the credentials were configured in IAM.

Hello Attila, If you run docker inspect proget -f '{{json .Mounts}}', does it include /var/proget/extensions as both the source and destination of one of the bind mounts?

Keep in mind that retention rules work on an AND basis, so when you select: Delete cached connector packages Delete old versions (all except latest 30 versions) You get only packages that match BOTH of those rules: Only delete cached packages. Never delete the most recent 30 versions of packages. I'm guessing that your packages don't match BOTH those rules;

There is currently no such healthcheck URL; you could use a static resource (like a logo, /resources/images/layout/logo.svg) to see if the web server is responding. That request should be very fast.

If you want developers to always be able to use any version of a package, then you should configure a connector to that remote resource. Then, they will always be able to download the latest version of the packages they need, and ProGet will cache those packages.

There is nothing to re-index. If you see it in the web, then it's already indexed. If the packages appear on the web page, then they will appear in the feed. You can manually inspect the feed with the API if you'd like, or by using a tool like Fiddler or something to see the requests.

Please note that retention policies are a paid feature. Although rules can still be configured in the free edition, they are always executed in dry run mode in ProGet Free. In addition, when multiple options are specified, then only packages that meet all of the selected criteria are considered. Please review the retention rules for more information Otherwise, the best place to look would be the retention logs, to show you what packages were considered.

There was a UI change; these are listed under "Containers" in the top UI.

You can use an API key: https://github.com/inedo/upack#push Basically just use "api" as username, and the key as the password.

Assuming you have only ProGet installed, delete the C:\ProgramData\upack directory. This is the location of the directory the Hub installer uses to detect the presence of any of the installed packages. If you have any of the other Hub software installed, you'll have to edit the installedPackages.json file in that directory and remove the entry for ProGet. We'll add a troubleshooting section to the documentation to cover this, and file a bug with the installer itself since this is not supposed to happen.

Please refer to KB#1161 for how to update to TLS 1.2

Maven indexes are for search only, and don't have any sort of sensible ordering, so you won't see packages like you would on npm feeds.

I don't know if there's a better endpoint for this, but I have NuGet feeds and I use a PowerShell script like this: $response = Invoke-WebRequest -Method GET -Uri https://{proget-host}/nuget/Default -UseDefaultCredentials $response.Headers["X-ProGet-Version"]

The connection string used by ProGet is stored in its configuration file (see this documentation page for the format and location). The Windows user account used is whatever user the INEDOPROGETSVC service is running under - generally, ProGet configures this to be NetworkService, but could be configured to be any user account.

Yes, we're currently using dotnet nuget push to push packages. We're using the "legacy" *.symbols.nupkg format, though, to be safe.