11 engineers on Hacker News describe using TeamCity first-hand: 2 endorse it, 2 regret it, 1 are mixed.
“In teamcity, we had close to 1k build configs... our devs were 'afraid' to alter teamcity build configs, as it all was more fragile than it should be”
regret · production · stingraycharles · 2026-10-06 · source ↗ · wrong label?“Having used Teamcity for CI I cannot think of a more clunky and hard to use system (compared to GHA, which is what we migrated to).”
regret · production · xp84 · 2026-04-29 · source ↗ · wrong label?“We switched to self hosted teamcity and 1/3 our build time with a 6 month payback.”
endorse · production · brianwawok · 2022-12-07 · source ↗ · wrong label?“we use teamcity which lets us pin our configurations to agents”
endorse · production · maccard · 2021-12-12 · source ↗ · wrong label?“It's really nice, but expensive if you exceed the limits for the free version (3 agents and 100 build configurations).”
mixed · production · stephen_g · 2017-12-25 · source ↗ · wrong label?“along with a TeamCity as a CI to run tests and deploy.”
neutral · production · victorNicollet · 2022-03-15 · source ↗ · wrong label?“We migrated from TeamCity and OctopusDeploy a couple of months ago and we are already regretting it.”
neutral · production · zeeshanejaz · 2019-01-24 · source ↗ · wrong label?“Build agents for TeamCity, this was one of the first scenarios and it's been amazingly helpful so far.”
neutral · personal · grownseed · 2014-10-17 · source ↗ · wrong label?“Whenever we update code in our source control system, a TeamCity server builds, runs the unit tests, integration tests, data tests, and then does a zero-downtime deployment”
neutral · production · MartinCron · 2011-02-20 · source ↗ · wrong label?