TeamCity publishes broken NuGet packages

We use TeamCity (7.0.3) both as a CI server, and a private NuGet feed. I have a lot of love for TC, but I currently have one major concern:

If my tests fail, TC still publishes the NuGet packages.

Not cool.

I raised this is an issue with JetBrains, and was told it was a feature request. And, that as a workaround, I could split my builds in two and separate the publish step from the rest of the build.

As far as I’m concerned, this is a showstopper bug. It introduces broken behaviour out of the box, which you won’t find out about until you realise a broken package is in use downstream. If JetBrains expects people to use TeamCity as a NuGet feed, this needs to be fixed.

(There’s also no (easy) way to remove packages from the feed, but I’m less concerned about that :) )

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s