Cloud Integrations - Features

Amazon EC2

TeamCity takes advantage of cloud computing by putting build agents on Amazon EC2.

TeamCity accounts for virtual machines in its build scheduling and automatically suspends/resumes them, based on the load and build queue status.

2019.1 Utilize AWS Spot Fleet requests for a more advanced and cost-effective way of running your builds on AWS.

2019.2 Create cloud build agents using EC2 launch templates, and modify their parameters in your AWS account, without changing anything in the TeamCity project configuration.

Microsoft Azure plugin

Using Microsoft Azure cloud platform? Integrate it with TeamCity and scale out your build farm when needed. Don't bother predicting load on your build agents during releases any more. TeamCity will automatically start agents on Azure when you need more power, and stop them, when they are no longer needed. The Azure Artifacts Storage plugin provides the ability to use Azure Blob Storage to keep external build artifacts.

Google Cloud plugin

TeamCity provides a tight integration with Google Cloud services. The Google Cloud Agents plugin allows using Google Compute Engine to start cloud instances on demand to scale the pool of cloud build agents and also supports using cost-efficient preemptible virtual machines. The Google Artifact Storage plugin provides the ability to use Google Cloud Storage to keep external build artifacts.

VMware vSphere

Integrate TeamCity with VMware vSphere and use remote TeamCity agents installed on VMware virtual machines to process builds more efficiently: TeamCity analyzes the build queue and launches virtual machines with the TeamCity agents matching queued builds.

Kubernetes

The TeamCity Kubernetes Support plugin by JetBrainslets you implement a scalable CI/CD architecture on top of Kubernetes: build agents can be launched automatically when you need them, do their job, and then be removed after the build completed.