You are viewing the documentation of TeamCity 10.x and 2017.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


This page covers general information about the configuration of integration. For the list of currently supported solutions, refer to Available Integrations.

On this page:

Table of Contents


Do the following:

  1. Complete the steps for creating a virtual machine.
    • Remove any temporary/history information in the system.
    • Stop the agent (under Windows, stop the service but leave it in the Automatic startup type)
    • (optional) Delete the content of the logs and temp directories in the agent home
    • (optional) Clean up the <Agent Home>/conf/ directory from platform-specific files
    • (optional) Change the buildAgent.properties file to remove the name, serverUrl, and authorizationToken properties unless otherwise specifically stated in the platform-specific documentation.
  2. Make a new image from the running instance. Refer the cloud documentation on how to do this.


Configuring a cloud profile in TeamCity

Agent Cloud Profiles are configured in the Server Administration UI, on the A cloud profile is a collection of settings for TeamCity to start virtual machines with installed TeamCity agents on-demand. Prior to TeamCity 2017.1, profiles are configured on the TeamCity | Administration | Agent Cloud page. In the later versions, cloud profiles  are configured at the project level, on the dedicated page of project settings.

Estimating Costs

The cloud provider pricing applies. Please note that the charges can depend on the specific configuration implemented to deploy TeamCity. We advise you to check your configuration and the cloud account data regularly in order to discover and prevent unexpected charges as early as possible.