Build your CI/CD pipeline with TeamCity for complete flexibility, scalability, and reliability. Whatever your infrastructure needs, TeamCity will support it.
Whether you’re a solo developer looking for an out-of-the-box solution or a development team searching for a CI/CD solution that will grow with you, TeamCity gives you the freedom to build where you want and scale your pipeline as your projects evolve.
Have full control over the environment where you run your builds.
Use Docker for any step of your pipeline and automate CI/CD for projects of any size.
Add as many build agents as you need to run more builds in parallel. Configure build pipelines in the most flexible way.
TeamCity allows you to set up any workflow that your team needs.
Hosted by JetBrains
Offload the hardware maintenance while retaining the flexibility to build where you want. Combine our off-the-shelf build agents with self-hosted agents in your private cloud or local network.
Hosted by you
Host TeamCity Server on Linux, Windows, or macOS in-house or in the cloud, and connect to build agents running on the infrastructure and platforms of your choosing.
Build on different platforms and mix and match local, self-hosted, and cloud-based infrastructure with TeamCity’s build agents.
Build agents are the software responsible for executing the tasks that make up your CI/CD pipeline, from checking out code, fetching packages, and loading Docker images to running scripts, reporting metrics, and forwarding build logs to the TeamCity Server.
Run your TeamCity agents on Linux, Windows, or macOS directly or via a Docker container and host them locally or in the cloud.
Each agent communicates with your TeamCity Server over a secure connection, enabling a highly customizable continuous integration and deployment process.
With no limit on the number of agents that you can connect and support for parallel builds, use TeamCity to create a highly available, performant pipeline that scales with your team.
Alongside extensive support for programming languages, testing frameworks, version control systems, and hosting services, TeamCity gives you the power and flexibility to build any project on any platform.
Manage your pipeline locally with build agents deployed to bare metal servers, virtual machines, or Docker containers. No need to choose between on-premises and cloud-hosted resources – simply connect cloud-hosted agents alongside your on-site build infrastructure when you need to expand.
Scale your build farm automatically with cloud-hosted build agents. TeamCity offers built-in support for Amazon EC2, VMware vSphere, and Kubernetes, as well as plugins for Windows Azure, Google Cloud, and more.
Get started quickly with managed build agents configurable to your needs. Get the best of both worlds and extend your fleet by connecting your existing on-premises or cloud-hosted build agents to TeamCity Cloud.
“We ended up with a hybrid cloud solution that included TeamCity Cloud Profiles and AWS. In addition to that, we had on-premises computers for build agents. This combination allowed us to accommodate any number of builds throughout the day, while also providing a baseline agent count for the off-hours. So we could run whatever we wanted wherever we wanted.”
– Yuri Trufanov, Executive Technical Director of Technology Platform, Playrix
At JetBrains, we recognize that no two software development projects are identical. That’s why we’ve designed TeamCity with flexibility at its core. Our fully customizable pipelines allow you to run automated builds and tests wherever you want, however you want.
Rapid feedback is at the heart of the DevOps methodology. If there’s an efficiency gain to be made, you can be sure that TeamCity offers it.
When you’re dealing with multiple projects and the demand for build infrastructure is high, “first-come, first-served” is not always the best approach. Use agent pools to ring-fence build resources for specific projects and ensure feedback is always delivered fast. Define which team members can access which build agents. See usage statistics in TeamCity. Learn more about configuring agent pools.
Accelerate automated tests with intelligent test parallelization. Allow TeamCity to identify opportunities to execute tests in parallel based on available build agents.
TeamCity will calculate the most efficient way to split tests across the available resources using test duration metrics from previous runs. Read about how to conduct parallel testing with TeamCity.
When a build or test fails, you want to investigate the cause immediately. Each TeamCity build agent automatically sends build logs, test results, and metrics to your TeamCity Server, so you have all the information at your fingertips.
As your CI/CD process evolves, you’ll want to ensure you have the right resources available while minimizing waste. TeamCity’s build agent statistics provide you with a clear picture of the load on your build farm, how demand varies, and any machines that are not performing well.
With a single TeamCity Server capable of managing hundreds of thousands of build agents and centralized management of build agent tools, you can use TeamCity’s powerful CI/CD platform without a dedicated team to manage it. All updates of build agents and plugins are delivered automatically, so you don’t have to worry about updating your tooling. Learn more about installing agent tools.
Not sure if TeamCity will work with your build infrastructure? Contact us and we’ll discuss how TeamCity can support your CI/CD processes.
You can run builds on Linux, Windows, and MacOS. Simply deploy build agents for the platforms you need. TeamCity supports a wide range of build runners to automate every step of your build and test pipeline – from checking out the latest changes and fetching dependencies to running build scripts, executing tests, and publishing artifacts.
Yes. With TeamCity, you can run builds on multiple platforms. It is recommended to have a separate build configuration for each sequence of builds.
Yes. You can deploy build agents to in-house servers and cloud-hosted infrastructure and connect them to the same TeamCity server. Use agent requirements and agent pools to control how build jobs are distributed between agents.
Yes. If you don’t want certain build steps to run, you can use conditional build steps to set this up. If you need certain actions to execute on a specific agent, use an additional (conditional) build step that will only be executed on this agent.
Powerful CI/CD system that supports any build configuration