TeamCity

TeamCity
Name	TeamCity
Developer	JetBrains
Released	2006
Latest release	2025.1
Programming language	Java, Kotlin
Operating system	Windows, Linux, macOS
License	Proprietary (Commercial, Free Professional)

TeamCity TeamCity is a continuous integration and continuous delivery (CI/CD) server developed by JetBrains. It provides build automation, test reporting, and deployment orchestration for software projects and integrates with version control, issue tracking, and cloud platforms. TeamCity is used by enterprises and open-source projects to streamline delivery pipelines and enforce quality gates.

Overview

TeamCity originated at JetBrains to support internal build automation and was publicly released to address needs similar to systems like Jenkins, Bamboo (software), Travis CI, CircleCI and GitLab CI/CD. The product competes in a landscape that includes offerings from Atlassian, GitHub, Microsoft Azure DevOps, Amazon Web Services, and Google Cloud Platform. TeamCity emphasizes configurability, rich diagnostics, and server-agent architecture influenced by earlier continuous integration concepts from CruiseControl and build automation tools such as Maven, Gradle, Ant (software), and Make (software). Enterprises such as Spotify, Etsy, BBC, and SAP have been cited in case studies adopting CI/CD platforms to accelerate delivery.

Architecture

TeamCity employs a master-agent model in which a central server coordinates distributed build agents running on diverse platforms including Windows Server, Ubuntu, Red Hat Enterprise Linux, and macOS. The server persists metadata and build history in databases like PostgreSQL, Microsoft SQL Server, Oracle Database, or MySQL. Agents execute build runners that invoke tools such as Docker, Kubernetes, Ansible, Terraform, Gradle, Maven, npm, and MSBuild. The system exposes REST APIs and integrates with authentication providers like LDAP, Active Directory, OAuth 2.0, and SAML. TeamCity supports remote run and pre-tested commit workflows influenced by practices described in literature from Martin Fowler and Kent Beck.

Features

TeamCity offers features including build chains, snapshot dependencies, artifact management, and failure condition rules inspired by best practices from Continuous Integration founders and case studies from ThoughtWorks. It provides parallel and matrix builds, build queuing, and artifact retention controls similar to capabilities in Bamboo (software) and Jenkins X. Test reporting includes flaky test detection and history analysis comparable to tools used by Google and Facebook. Build configuration can be managed via web UI or Kotlin-based project configuration as code, echoing infrastructure-as-code patterns popularized by HashiCorp and Chef (company). Security features align with guidance from OWASP and compliance frameworks from ISO/IEC 27001.

Integration and Plugins

TeamCity integrates natively with version control systems such as Git, Subversion, Perforce, Mercurial, and Azure Repos. It supports issue tracker linking with JIRA, YouTrack, GitHub Issues, and GitLab Issues. Plugin ecosystems add capabilities for code coverage tools like JaCoCo, Cobertura, and Istanbul, static analysis from SonarQube and SpotBugs, and notification channels including Slack (software), Microsoft Teams, Email, and PagerDuty. Community and commercial plugins are developed by organizations including JetBrains, independent contributors, and vendors in the DevOps tooling space; integrations often mirror connectors provided by Atlassian Marketplace and GitHub Marketplace.

Deployment and Administration

Administrators deploy TeamCity on-premises, in hybrid models, or in cloud environments such as Amazon EC2, Google Compute Engine, Microsoft Azure Virtual Machines, and container platforms like Docker Swarm and Kubernetes. High-availability patterns use DB clustering strategies recommended by PostgreSQL and Microsoft SQL Server documentation. Backups and disaster recovery align with practices from Red Hat and IBM enterprise operations. Monitoring integrates with observability systems such as Prometheus, Grafana, New Relic, and Datadog to surface metrics and alerts. Security hardening follows guidance from CIS benchmarks and corporate policies from organizations like Fortinet.

Licensing and Editions

TeamCity is offered under commercial licensing by JetBrains with Free Professional editions available for small teams or open-source projects; licensing tiers are comparable to models used by Atlassian and Perforce. Enterprise customers may negotiate support and maintenance agreements similar to arrangements provided by Red Hat and Oracle Corporation. Licensing impacts agent counts, feature sets, and support levels, and organizations evaluate total cost of ownership versus cloud-native CI/CD services such as CircleCI and Travis CI.

Adoption and Use Cases

TeamCity is used across industries including finance firms like Goldman Sachs, media companies like BBC, technology firms like JetBrains itself, and open-source foundations. Common use cases include continuous integration pipelines for Java, .NET, and JavaScript applications; automated testing for frameworks such as JUnit, NUnit, Selenium (software), and Cypress (software); containerized builds using Docker; and deployment orchestration to Kubernetes clusters, AWS Elastic Beanstalk, and Azure App Service. Organizations pair TeamCity with configuration management tools from Puppet (software), Chef (company), and Ansible to implement end-to-end delivery workflows and compliance controls used in regulated sectors overseen by bodies like PCI DSS and HIPAA.

Category:Continuous integration software