ProGet and Feed Updates

I have a process that posts CI builds to a NuGet feed. To cleanup the disk, I have another process that finds the stale CI packages in the feed and deletes them and restarts the ProGet service. Upon restart, ProGet would update the DB and the stale records would be removed from the UI. That's been working great for years

I have another process I follow on releasing a product. I take a CI package that reflects a product release and do a little "manual promotion" by moving it from the "build" feed and into a "release" feed via the release feed's drop path. The release feed is connected to the build feed by a connector. ProGet would notice the move and update the record for the package to point to it in the release feed. These two procedures have been working great for years.

Sometime in the last month I upgraded to 4.8.7 and today noticed a problem. First, while the package I moved into the release feed's drop path would move into the correct subfolder of the release feed, the ProGet record for that package failed to update. Rather than notice that the package no longer exists in the build feed and was just added to the release feed, ProGet continues to attempt to serve the package from the build feed. As a result, client pulls (which always utilize the single build feed) are failing to fetch the package. I've only been able to fix this by deleting the package and manually reloading it in the release feed.

Second, it looks like ProGet has stopped syncing its database with what's on the file system upon restart. My delete process leaves only 15 CI packages in the build feed, but there's now a couple hundred dead links in the "All Versions" section for the package for every CI build I've been posting to my "build" feed.

I've restarted ProGet and the services a couple times, but that hasn't helped. What can I do to get ProGet to resync back up with whats actually on the file system? It seems like the two problems I've mentioned could be related in that my "build" feed isn't being updated like it once was. I'd be OK upgrading to 4.8.9, but the issues addressed don't appear related to this issue.

Thanks

Product: BuildMaster
Version: 5.8.2

Directly accessing/modifying packages within a package store (either database or disk) was not/never supported. It happened to work, at the time, because of the feed cleanup task would reconcile the database/store.

However, this caused more problems than benefits, so as of ProGet 4.8, the feed cleanup task will no longer attempt to reindex packages if they have been deleted/edited outside of ProGet; see KB#1148.

You should use either retention policies or the API to query/delete packages from ProGet.

Thanks for the answer and bummer I didn't connect that dot when reviewing the upgrade procedures.