The TeamCity Anka Build Cloud provides a quick way to integrate Anka Build Cloud with TeamCity. The plugin will dynamically provision Anka VM instances for building, testing, and more.
The TeamCity plugin requires a VM with Java, SSH Remote Login, port-forwarding, and TeamCity:
System Properties) and look for
java.version is set to
1.8.0_242, you can download and install the AdoptOpenJDK jdk8u242-b08.pkg.
System Preferences > Sharing).
curl -O -L https://download.jetbrains.com/teamcity/TeamCity-$TEAMCITY_VERSION.tar.gz
tar -xzvf TeamCity-$TEAMCITY_VERSION.tar.gz
mv Teamcity/BuildAgent /Users/anka/buildAgent
echo >> buildAgent/conf/buildagent.properties (Do not delete it)
sh BuildAgent/bin/mac.launchd.sh load and then wait a minute before continuing.
sudo anka suspend <VM Template name>
sudo anka registry push <VM Template name> <Tag name>
These steps are based on TeamCity 2019.2.4. Your version and UI may differ slightly.
Install the Anka Build Cloud plugin: Browse to
Administration > Plugins List and upload the
Under Edit Project for your project, navigate to Cloud Profiles.
Click on Create new profile and choose
Anka Build Cloud for the Cloud type.
It's a good idea to set the Server URL to your TeamCity address and port (including
http[s]://). Otherwise, TeamCity could pass the wrong serverUrl to the VM (if you're running TeamCity on a non-default port).
For Additional terminate conditions, check the box for After first build.
For Controller URL, enter Anka Build Cloud Controller IP and port. Default port is 80.
Once the connection is successful to the Controller, Image Name will show all VM templates from the Registry. Select the one you want to use for your project.
Image Tag will show all Tags for the selected VM Template (
"Image Name"). Select the one you want to use or leave it to
Latest to always use the latest Tag.
For Group you can define the specific group to run the VMs on (Available only in Enterprise and Enterprise Plus Tiers).
SSH User and SSH Password are the default, unless you've changed the user for the VM, logins (anka/admin).
Agent Path Select is the path to TeamCity agent location in the VM (don't modify this unless you installed TeamCity outside of the anka user home directory.
Enter Priority the VM will take when scheduling the instance start (Available only in Enterprise and Enterprise Plus tiers).
Once saved, you will now see the object under your Agents page named after the
Image Name you chose in the configuration/setup.
Anytime you execute a build for the project, it will request a new VM from the Anka Build Cloud Controller and wait for it to start. Once started, the plugin will SSH into the VM and add the necessary values to the
buildAgent.properties config. The Agent will then start and run your job. It's important to ensure that access from TeamCity to the Node (which hosts the VMs), VM (using port-forwarding), and then from the VM itself back to TeamCity is possible.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.