Jetbrains TeamCity

What is included in JetBrains TeamCity?

Build automation – Automatically builds, tests, and deploys code changes.
Pipeline as code – Define pipelines in Kotlin DSL or visually.
Build chains – Visualize and orchestrate dependent builds across projects.
Test intelligence – Tracks flaky tests and full test history.
Core Capacity – Free edition includes 3 agents, 100 configurations.
Important – Unlimited build configurations require the paid Enterprise edition.

What are the main benefits of JetBrains TeamCity?

JetBrains TeamCity is a continuous integration and delivery server that automates building, testing, and deploying software across on-premises, cloud, and hybrid setups. It centralizes build management for teams working with Git, Perforce, Maven, Gradle, .NET, Docker, and the JetBrains IDE ecosystem.

Built-in features – Works out of the box without plugin sprawl.
Fast feedback – Notifies developers the moment a build breaks.
Parallel builds – Run builds concurrently across multiple agents.
IDE integration – Triggers and views builds inside IntelliJ IDEA.
Flexible hosting – Deploy on-premises, in the cloud, or hybrid.
Pre-tested commits – Validate changes before they reach the repository.

What does JetBrains TeamCity do?

TeamCity is a CI/CD server that automatically builds, tests, and deploys your code whenever changes are pushed to version control. It monitors repositories such as Git, Perforce, and Subversion, then triggers builds from rules you define and reports results through a web interface. A central server coordinates the work while distributed build agents run the actual build and test jobs in parallel. This gives developers immediate feedback when a commit breaks the build, instead of surfacing problems late in a release cycle.

Who is JetBrains TeamCity best suited for?

TeamCity fits software teams that want a polished, self-hosted CI/CD server without assembling and maintaining a large plugin stack. It is especially strong for JVM and .NET shops, since it ships first-class Maven, Gradle, Ant, and MSBuild runners and integrates tightly with IntelliJ IDEA, Rider, and other JetBrains IDEs. A small team can run the free Professional edition with 3 build agents and 100 build configurations, while larger organizations move to Enterprise for unlimited configurations. Teams already on JetBrains tooling also get remote runs and pre-tested commits directly inside their IDE, which Jenkins does not provide out of the box.

What is the difference between TeamCity Professional and Enterprise?

The main difference is scale: TeamCity Professional is free but capped at 100 build configurations and 3 build agents, while Enterprise removes the configuration limit entirely. Both editions install from the same distribution and share the same core features, so you switch by entering a license key without losing any data. Enterprise adds priority support through a private Zendesk instance, whereas Professional relies on the community forum and public issue tracker. Each additional build agent you add raises the Professional configuration limit by 10 and lets one more build run in parallel. TeamCity Cloud is a third option, hosted by JetBrains on a credit-based model instead of self-hosted.

Which version control systems and build tools does TeamCity integrate with?

TeamCity supports Git, Perforce, Mercurial, Subversion, and CVS out of the box, with dedicated integrations for GitHub, GitLab, Bitbucket, and Azure DevOps. A single build can pull source from several repositories at once, even mixing VCS types such as Perforce and Git in one configuration. On the build side it includes runners for Maven, Gradle, Ant, MSBuild, NuGet, Node.js, and Kotlin Script, and any step can run inside a Docker container. For scaling agents, it connects to Amazon EC2, Kubernetes, VMware vSphere, Google Cloud, and Azure.

What should teams know before choosing the free Professional edition?

The free Professional edition is fully featured but hard-capped at 100 build configurations and 3 build agents, and exceeding the agent limit blocks new builds from starting until you add capacity. Scaling past that requires the paid Enterprise license plus additional agent slots, each adding 10 configurations. The AI Assistant is a paid Enterprise integration, not a free feature. TeamCity is also a JVM application with a relatively high memory footprint, and its project hierarchy and build-chain model carry a learning curve during first-time setup. Open-source projects can avoid the cost by applying for a free license through the JetBrains program.

What changed in TeamCity 2026.1 that buyers should know about?

Starting with version 2026.1, the TeamCity server and build agents no longer start under Java versions older than 21, so the host must run Java 21 to launch the server. This requirement only affects running TeamCity itself; your builds can still target older Java versions such as JDK 19. The release also adds a TeamCity CLI for managing builds from the terminal and an MCP endpoint that lets AI agents interact with the server. On-premises versions now receive two major releases per year, while TeamCity Cloud updates more frequently.

Does TeamCity run on Windows, Linux, and macOS?

Yes. The TeamCity server and build agents are Java-based and run on recent versions of Windows, Linux, and macOS, as well as in Docker containers. The Windows installer and Docker images bundle Amazon Corretto Java 21, while Apple Silicon hosts such as M1 or M2 are best paired with a build like Azul OpenJDK.

How is TeamCity different from Jenkins?

TeamCity is a proprietary JetBrains product that ships build chains, test history, and Kotlin DSL pipelines out of the box, whereas Jenkins is open source and depends heavily on community plugins for comparable features. Teams typically pick TeamCity for a faster, more consistent setup with vendor support, and Jenkins for maximum flexibility with no license cost.