Published to TeamCity NuGet feed not including all artifacts in feed

In my project i have bunch of artifacts (about 10 .nupkg files are there under artifacts). however octopus nuget feed is not able to detect any of them.

This started since we upgraded to 2018.1 version from 2017.X

I tried doing the Administrator -> diagnostics --> Reset buildMetadata as suggested in some articles but to no avail.

Can someone pleas help me figure out what is going on?

 

3
8 comments

Same here, example logs (teamcity-nuget.log): 

 

[2018-07-02 14:26:37,728] INFO - NuGetBuildMetadataProviderImpl - Indexing NuGet package from artifact Company.ApplicationName.NotificationService.1.4.0-unstable0054.nupkg of build #1.4.0-unstable.54 {build id=9004, buildTypeId=ApplicationName_ReleaseConfiguration}
[2018-07-02 14:26:39,213] INFO - NuGetBuildMetadataProviderImpl - Indexing NuGet package from artifact Company.ApplicationName.Migrations.1.4.0-unstable0054.nupkg of build #1.4.0-unstable.54 {build id=9004, buildTypeId=ApplicationName_ReleaseConfiguration}
[2018-07-02 14:26:39,515] INFO - NuGetArtifactsMetadataProvider - Added NuGet package company.applicationname.notificationservice.1.4.0-unstable0054 from build #1.4.0-unstable.54 {build id=9004, buildTypeId=ApplicationName_ReleaseConfiguration} into feed _Root
[2018-07-02 14:26:39,515] INFO - NuGetArtifactsMetadataProvider - Added NuGet package company.applicationname.migrations.1.4.0-unstable0054 from build #1.4.0-unstable.54 {build id=9004, buildTypeId=ApplicationName_ReleaseConfiguration} into feed _Root
[2018-07-02 14:26:39,580] INFO - NuGetArtifactsMetadataProvider - Added NuGet package company.applicationname.notificationservice.1.4.0-unstable0054 from build #1.4.0-unstable.54 {build id=9004, buildTypeId=ApplicationName_ReleaseConfiguration} into feed _Root
[2018-07-02 14:26:39,581] INFO - NuGetArtifactsMetadataProvider - Added NuGet package company.applicationname.migrations.1.4.0-unstable0054 from build #1.4.0-unstable.54 {build id=9004, buildTypeId=ApplicationName_ReleaseConfiguration} into feed _Root
[2018-07-02 14:50:01,362] INFO - NuGetBuildMetadataProviderImpl - Indexing NuGet package from artifact Company.ApplicationName.Migrations.1.4.0-unstable0055.nupkg of build #1.4.0-unstable.55 {build id=9007, buildTypeId=ApplicationName_ReleaseConfiguration}
[2018-07-02 14:50:01,657] INFO - NuGetArtifactsMetadataProvider - Added NuGet package company.applicationname.migrations.1.4.0-unstable0055 from build #1.4.0-unstable.55 {build id=9007, buildTypeId=ApplicationName_ReleaseConfiguration} into feed _Root
[2018-07-02 14:50:03,716] INFO - NuGetArtifactsMetadataProvider - Added NuGet package company.applicationname.migrations.1.4.0-unstable0055 from build #1.4.0-unstable.55 {build id=9007, buildTypeId=ApplicationName_ReleaseConfiguration} into feed _Root
[2018-07-02 14:50:05,775] INFO - NuGetArtifactsMetadataProvider - Added NuGet package company.applicationname.migrations.1.4.0-unstable0055 from build #1.4.0-unstable.55 {build id=9007, buildTypeId=ApplicationName_ReleaseConfiguration} into feed _Root

 

Basically it gets stuck at some point probably the indexer is running too soon and cannot pickup all of the artifacts in time.

0

I also noticed that "Published to TeamCity Nuget Feed" is not listing all packages it created in build or ones in artifacts for that build.

There is no error in teamcity.server.log. What is interesting, with same build configuration in the past, C:\ProgramData\JetBrains\TeamCity\system\artifacts\<builder>/<BuildNumber>/ .teamcity\nuget\packages.json used to indicate all packages that build spits out. Now it just lists one of the nupkg file from artifacts.

0

For now I did workaround by adding Nuget publish build step to forcefully push the packages that teamcity is not detecting but for projects which are still refering some of my old version of dlls through  internal nuget (which i lost from feed due to this reindexing issue) which i can not upgrade without lot of work.

0

@Vishal, there is a know problem that the only first NuGet package is available in the feed in 2018.1: TW-55703

To resolve it you need to install the plugin with a fix from this issue.

0

Thanks @Dmitry. Just tried new build with plugin and it did worked. 

0

Yes it did help, thanks.

0

Hi All, I have recently updated from 2018.2.4 to 2019.1.5 and having a similar issue as listed above, can you please clarify which plugin you needed to update. Was it nuget? or Octo integration? or a different plugin all together?

0

Hi Todd,

 

the issue reported here was fixed in 2018.1, so if you are seeing it in 2019.1.5 either it was a regression that we have not seen reported elsewhere or your issue is somewhat different. Please provide exact details so that we can track it down.

0

Please sign in to leave a comment.