TeamCity NuGet feed showing cleaned up artifacts as available

We are currently having an issue using TeamCity as a NuGet feed for our development packages.

TeamCity is still listing packages as being available for use after the build artifacts they depend on have been deleted by our retention policies. If we try to download one of the packages from the feed we get a 404 not found error.

We are adding them to the feed using the NuGet pack build step and tick the "Publish created packages to build artifacts".

We are running TeamCity 8.1.4 but it was also happening on 8.1.3.

Has anyone come across this and possibly shed some light on the subject?

5 comments
Comment actions Permalink

Hi,

To delete NuGet packages please run clean-up. Also removing of a build will remove associated with it packages.
See related issue.

0
Comment actions Permalink

The artifacts are being removed by our Clean-Up process however they are still being shown as available in the feed. Do we have to remove build history as well?? If this is the case we may have to stop using the TeamCity NuGet feed.

I have attached our Clean-Up rules.



Attachment(s):
cleanup.png
0
Comment actions Permalink

No, build history should not be deleted. While clean-up artifacts are deleted and re-indexing is performed, so after it there should be no deleted packages listed in TeamCity feed.
How do you check that packages are still listed in TC feed? Please attach teamcity-server.log and teamcity-cleanup.log files.

0
Comment actions Permalink

This is still an issue in 2019.1.3. Build artifacts are cleaned up and not shown in the TC UI, but using NuGet to query the feed it lists all of the artifacts from all versions.


E.g. with the command nuget list MyPackage -source "https://myteamcity.blah.com/httpAuth/app/nuget/feed/MyProject/MyFeed/v2" -allversions -prerelease

0
Comment actions Permalink

HI Kuan, 

Thank you for creating an issue in YouTrack. We can reproduce the problem and will include the fix in the next bugfix release (which is going to be released next week).

0

Please sign in to leave a comment.