TeamCity

TeamCity is JetBrains' CI/CD server for build, test and deploy pipelines, self-hosted on a team's own servers or run as the hosted TeamCity Cloud.

TeamCity builds and tests each change a team commits and carries the result through to deployment. JetBrains owns and develops it alongside its IDEs and other developer tools, and has made software for programmers since 2000. It comes in two editions: TeamCity On-Premises, a server installed on the team's own infrastructure, and TeamCity Cloud, which JetBrains hosts. Both keep build settings as code beside the project source, in Kotlin or XML for build configurations and in YAML for the newer pipelines. Work starts from VCS triggers on each commit and on pull request branches, or from schedule triggers at a set date and time. Build chains link configurations into one flow, and artifact dependencies hand one build's output to the next. Matrix builds generate a build for every combination of parameter values, while the Build Cache keeps downloaded files between runs so jobs skip fetching them again. Build Approval holds a build until named users or groups approve it, and password parameters hide secrets from the interface and the logs, with HashiCorp Vault as a remote secret store. Test reports feed a Flaky Tests tab, failing tests can be investigated or muted, and statistic charts follow success rate, duration and queue time across a configuration's history. The On-Premises edition suits teams that want the whole CI server and its agents under their own control, on their own machines or in their own Kubernetes cluster. The Cloud edition suits teams that would rather not operate a server, with JetBrains-hosted agents on Windows Server, macOS and Ubuntu, Arm64 machines included, and the option to attach agents of their own. Developers who already write code in JetBrains IDEs get a build server from the same company. Projects built with Maven, Gradle or .NET tooling, and teams that store CI configuration as Kotlin code in their repositories, fit it as well. A common setup compiles, tests and packages on every pull request, then waits for approval before a deployment build starts. Code comes from GitHub, builds use Docker or run on Kubernetes agents, and its integrations reach Azure Boards. Template build configurations and meta-runners let a platform team define shared steps once and reuse them across many projects. AI agents can also work with TeamCity through MCP and its command line tool. TeamCity fits teams that want one CI system to cover their own build machines and hosted ones together.