Issues with Teamcity 2018.1 and Octopack Plugin Integration

In the new 2018.1 release of TeamCity they have altered when and how .nupkg files are index for their internal nuget server (Using TeamCity as NuGet Server).
The Octopack-Teamcity plugin use to handle this seamlessly.

However after the 2018.1 TC update only one package per build seems to be getting added to the internal feed (we often have have numerous packages created). The artifacts are still correctly being generated and can be viewed in TC, just not being correctly indexed for the internal TC nuget feed and are not visible in/to Octopus. This is after ensuring the nuget feed is enabled and the re-index packages build feature is on for the projects. The work around has been to add Nuget publish package steps to the build configurations. Hopefully this report is helpful (and its not just something specific to our environment), please let me know if I can provide further information. Thank you.

Versions: Octopus 4.1.5, Octopack 4.34.0, TeamCity 2018.1 (build 58245)

After further research, found that this appears to be an issue with the TeamCity release generally. As described here:

This fixed the problem and Octopus is working correctly. Thank you.

HI Thomas,

Sorry for the delay here. Thanks for getting back and letting us know about the workaround!


This fixed it for me too, although it was Octopus Support who pointed me in the right direction.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.