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!
'Usage & Statistics' info missing
-
Hello,
I'm using the free version of ProGet Version 2025.13 (Build 12) (Docker/ Linux). I uploaded my packages to the feed. Then I uploaded an 'SCA build' using pgutils and I can click on it in Web UI. There I have a list of all packages and I can click on the package name and it redirects me to the package page. By clicking the 'Usage & Statistics' tab there's "There are no active Builds using this Package" info shown.
Why is my package not listed? Is this an expected behavior? What should I do to view my package usage? Or is it available only in paid version?
I also tried restarting, reanalyzing the build but nothing have worked.
-
Hi @k-lis_1147,
Based on what you described, it should show up.
Can you confirm what feed type you're using, and whether or not you're using PostgreSQL (this is the default for ProGet 2025).
I just discovered a bug (PG-3145) that would impact PostgreSQL (all feeds probably) and certain feed types on SQL Server (Maven) that would cause that information not to display on that page.
Easy fix, but just want to double-check
Thanks,
Steve
-
I'm using NuGet feed with PostgreSQL.
-
After upgrading to Version 2025.14 (Build 12) the info is shown for the specific version of the package only.
Example:
- If I go to package A (version 1.0.0) usage page (/feeds/my-nuget-feed/A/1.0.0/usage) - it shows the project using that package correctly.
- If I go to package A (all versions) usage page (/feeds/my-nuget-feed/A/versions/usage) - it shows 'There are no active Builds using this Package.'.
I would expect the latter to display the build shown in the version 1.0.0 usage page.
-
Hi @stevedennis
is this problem being investigated?
-
Hi @k-lis_1147,
Sorry on the slow reply; we did not get a chance to investigate in last release, but it was on the list this week. That being said, it was also an easy fix (didn't anticipate it to be a copy/paste fix)-- and we'll get it via PG-3160 in this week's mainteancne release.
Thanks,
Steve
