TeamCity

Basic Information

TeamCity is a build management and continuous integration/continuous delivery (CI/CD) server developed by JetBrains. It automates the build, test, and deployment processes for software projects across various platforms and technologies.

• Model: CI/CD Server
• Version: Not applicable (CI/CD server)
• Release Date: October 2, 2006
• Minimum Requirements:
  • Server: 4 CPU cores, 4GB RAM (for small teams).
  • Agent: ~500MB RAM, minimal additional CPU.
• Supported Operative Systems: Windows (7/7x64, 10, 11, Server 2008-2022), Linux (Ubuntu, Debian, RedHat, SUSE, others), macOS.
• Latest Stable Version: 2025.07.2
• End of Support Date: Not explicitly defined; access to updates is tied to subscription.
• End of Life Date: Not explicitly defined.
• License Type: Freemium (Professional Edition is free for up to 100 build configurations and 3 agents, Enterprise features require paid licensing). Perpetual license for on-premises.
• Deployment Model: On-premises and Cloud.

Technical Requirements

• RAM:
  • Server: 8GB for up to 100 concurrent builds, 16GB for more loaded servers or larger repositories.
  • Agent: Approximately 500MB.
• Processor:
  • Server: Dual-core 3.2 GHz for modest setups (e.g., 60 projects, 300 build configurations, 50 agents). Intel Xeon E5520 2.2 GHz (4 cores, 8 threads) for heavily loaded servers (e.g., 150 projects, 1500 build configurations, 100 agents).
  • Agent: Minimal additional CPU time beyond the build process itself.
• Storage:
  • Server: Single HDD for modest setups; 3 HDD RAID1 (one general, one for artifacts/logs/caches, one for database) for loaded servers.
  • Agent: Dependent on build processes, including source checkout, downloaded artifacts, and build output.
• Display: Not applicable for server or agent components.
• Ports: Default HTTP port 8111, configurable for HTTPS.
• Operating System: Recent versions of Windows, Linux, or macOS.

Analysis of Technical Requirements

TeamCity's technical requirements are highly scalable, adapting to the workload and number of concurrent builds. The server demands more resources, particularly RAM and CPU, as the number of projects, build configurations, and users increases. Agent requirements are primarily driven by the builds they execute, with a baseline memory footprint. Disk I/O is a critical factor for performance, especially for the server and artifact storage. The flexibility to run on various operating systems for both server and agents provides broad deployment options.

Support & Compatibility

• Latest Version: 2025.07.2
• OS Support:
  • Server: Windows (7/7x64, 10, 11, Server 2008, 2012, 2016, 2019, 2022), Linux (Ubuntu, Debian, RedHat, SUSE, others), macOS.
  • Agent: Windows (7/7x64, 10, 11, Server 2003, 2008, 2012, 2016, 2019, 2022), Linux, macOS.
• End of Support Date: No fixed end-of-support dates are published; continued access to updates and priority support is typically provided through active subscriptions.
• Localization: No specific UI localizations are widely advertised, but the platform is used globally.
• Available Drivers: Supports external databases including MySQL (5.7.34+), PostgreSQL (9.6+), Oracle (10g+), and MariaDB (10.2+). An internal HSQLDB database is available for evaluation purposes.

Analysis of Overall Support & Compatibility Status

TeamCity demonstrates strong compatibility across major operating systems for both its server and build agents, ensuring broad applicability in diverse IT environments. It integrates with a wide array of development tools, version control systems (e.g., Git, GitHub, GitLab, Bitbucket, Subversion, Perforce), and build tools (e.g., Maven, Gradle, MSBuild, Ant). While specific end-of-support dates are not publicly detailed, JetBrains provides ongoing updates and support for active subscribers. The availability of drivers for popular external databases further enhances its adaptability for production environments.

Security Status

• Security Features: Disposable build environments and agents, agent pools for job isolation, clean checkout for source code integrity, SSH keys for secure VCS access, secure storage for sensitive data (password-typed parameters), CSRF protection, configurable HTTPS access, HashiCorp Vault integration, Content Security Policy. Integration with Snyk for open-source vulnerability scanning is also available.
• Known Vulnerabilities:
  • CVE-2024-27198: Critical (CVSS 9.8) authentication bypass vulnerability in the web component, allowing unauthenticated remote code execution (RCE) and full administrative control.
  • CVE-2024-27199: High (CVSS 7.3) authentication bypass and path traversal vulnerability, allowing limited information disclosure and system modification.
  Both vulnerabilities affect all TeamCity On-Premises versions prior to 2023.11.4 and have been actively exploited.
• Blacklist Status: Not applicable.
• Certifications: No specific security certifications are publicly listed.
• Encryption Support: SSH keys are stored encrypted in the TeamCity Data Directory. HTTPS access to the server is configurable.
• Authentication Methods: Internal database, Windows Domain, LDAP, various Git hosting providers (e.g., GitHub, GitLab, Bitbucket, Azure DevOps, JetBrains Space), HTTP SAML 2.0 (supporting Okta, OneLogin, AWS SSO, AD FS), Token-Based Authentication (introduced in 2019.1), Basic HTTP Authentication, and NTLM HTTP Authentication.
• General Recommendations: Promptly upgrade TeamCity On-Premises to version 2023.11.4 or newer. If immediate upgrade is not possible, apply the provided security patch plugin. Protect the TeamCity Data Directory with restricted access. Exercise caution when building public pull requests, using isolated or disposable agents.

Analysis on the Overall Security Rating

TeamCity incorporates a comprehensive suite of security features designed to protect the CI/CD pipeline, including mechanisms for isolated build environments, secure access to version control systems, and robust authentication options. However, the recent discovery and active exploitation of critical authentication bypass vulnerabilities (CVE-2024-27198 and CVE-2024-27199) highlight the importance of diligent patching and adherence to security recommendations. While the platform offers strong defensive capabilities, the impact of these vulnerabilities underscores that timely updates are crucial for maintaining a secure posture.

Performance & Benchmarks

• Benchmark Scores: Specific, standardized benchmark scores are not widely published.
• Real-world Performance Metrics:
  • Capable of handling up to 100 concurrently running builds with a server configuration of Intel 3.2 GHz dual-core CPU and 8 GB RAM.
  • More loaded servers can manage over 1500 builds a day with an Intel Xeon E5520 2.2 GHz (4 cores, 8 threads) and 16 GB RAM.
  • Highly scalable, supporting multiple build agents and projects simultaneously.
  • Features like faster build history cleanup contribute to improved server maintenance performance.
• Power Consumption: Not explicitly detailed, but larger installations can have high resource usage.
• Carbon Footprint: Not explicitly detailed.
• Comparison with Similar Assets:
  • Often compared to Jenkins (open-source, free, large community support).
  • Compared to CircleCI (noted for speed, cloud/on-prem options).
  • Compared to GitLab CI/CD (easy to use, secure, flexible).

Analysis of the Overall Performance Status

TeamCity is engineered for high performance and scalability, capable of managing complex CI/CD workflows across a wide range of project sizes. Its performance is directly tied to the underlying hardware infrastructure, with recommendations for CPU, RAM, and storage scaling based on the number of concurrent builds and overall workload. While specific benchmark figures are not readily available, user feedback and architectural design indicate its ability to handle demanding continuous integration and delivery tasks efficiently. Resource usage can be high for extensive deployments, necessitating careful planning of server and agent specifications.

User Reviews & Feedback

User reviews consistently highlight TeamCity's strengths in automation, reliability, and its user-friendly interface. Many praise its powerful features and seamless integration with various development tools, including support for the .NET framework. The ability to automate builds for load testing and its real-time reporting capabilities are also frequently cited as benefits.

However, common weaknesses include the pricing, which can be high for larger teams, and a perceived lack of comprehensive documentation for initial setup, particularly for API integration. Some users note a steeper learning curve without dedicated team support and mention that compulsory upgrades can occasionally disrupt ongoing work. The platform's resource usage can also be high.

TeamCity is recommended for medium to large businesses, particularly in software development, IT, and e-commerce, that are looking to streamline and scale their continuous integration and delivery processes. It is well-suited for companies expanding their software development operations and needing a reliable tool for automated testing and deployment.

Summary

TeamCity is a robust and highly scalable CI/CD server designed to automate and streamline software development workflows. Its strengths lie in its comprehensive feature set, broad compatibility with operating systems and development tools, and its ability to handle complex build and deployment pipelines. The platform offers extensive authentication methods and security features like disposable agents and encrypted SSH keys, aiming to secure the development process.

However, recent critical authentication bypass vulnerabilities (CVE-2024-27198 and CVE-2024-27199) underscore the necessity for vigilant security practices and prompt updates. While praised for its user-friendliness and reliability, some users find its pricing model for larger teams and resource consumption to be drawbacks.

Overall, TeamCity is an excellent choice for organizations seeking a powerful and flexible CI/CD solution, especially those with diverse technology stacks and a need for high scalability. Recommendations include prioritizing immediate upgrades to the latest patched versions (2023.11.4 or newer) or applying security patches to mitigate known vulnerabilities. Additionally, careful planning of hardware resources is essential to optimize performance for demanding workloads.

Information provided is based on publicly available data and may vary depending on specific device configurations. For up-to-date information, please consult official manufacturer resources.