On this page:
TeamCity vSphere integration allows using TeamCity agent cloud features with VMWare vSphere installation. It requires configuring TeamCity with your VMWare vSphere account and then handles automatic creation/starting/stopping/deleting of the virtual machines with TeamCity agents on-demand, based on the queued builds.
Before you can start using vSphere integration, you need to create a Virtual Machine with the TeamCity Build Agent installed and set to start automatically. Also, you need to manually point the agent to an existing TeamCity server with the vSphere plugin installed and start build agent to let the build agent download the plugins.
Depending on the type of the virtual machine used, the plugin behavior is different:
TeamCity will clone the selected virtual machine or a template and start to run the build; the clone will be stopped and deleted after it becomes unnecessary: when the build is finished or an idle timeout elapses, depending on the profile settings. To use this behavior, you need a virtual machine or a template.
If you select to start an existing virtual machine, it will be is started before a build and stopped after it becomes unnecessary: when the build is finished or an idle timeout elapses, depending on the profile settings.
The following steps are required to set up TeamCity-WMware vSphere agent cloud integration:
- Download the TeamCity-WMware vSphere plugin.
- Install the plugin on the TeamCity Server.
- Create a virtual machine where your builds will run. Refer to the VMware vSphere web site for details on creating virtual machines.
- Prepare a machine with an installed TeamCity agent.
- If you want TeamCity to start/stop this machine on demand or to clone it, proceed to configuring the WMware cloud profile on the TeamCity server.
- If you want to create a template of this machine and clone it, refer to the VMware vSphere web site for details on creating templates and proceed to configuring the WMware cloud profile on the TeamCity server.
For step-by-step instructions, see the related blog-post.
TeamCity Versions Compatibility
The current build status is
Detailed CI status page