TeamCity integration with Yandex Compute Engine which allows using cloud instances to scale the pool of build agents.
The plugin is compatible with TeamCity 10.0.x and greater.
You can download the plugin and install it as an additional TeamCity plugin.
The plugin supports Yandex Compute images to start new instances.
You need to create a service account, assign the Editor or Admin roles
and create JSON private key
for this service account
Before you can start using the integration, you need to create a new cloud image. To do that, create a new cloud instance, install the TeamCity Build Agent on it and set it to start automatically. You also need to manually point the agent to the existing TeamCity server with the Yandex Cloud plugin installed to let the build agent download the plugins.
Then install required build tools and remove temporary files.
Then you need to create a new image from the instance disk. You can do this by two ways:
yc compute disk list
yc compute image create --name teamcity-agent --source-disk-id=DISK_ID
Now you need to delete instance.
To create a Yandex agent cloud profile, navigate to the project where you want to set up the profile and select the Cloud Profiles link. Then click the “Create new profile” button and select “Yandex Compute” as the cloud type. Specify the profile name and the JSON private key value in the corresponding field.
To add a new image to the profile, press the “Add image” button, select the recently created cloud image, and fill in other properties. Next you need to save the image and then the profile settings.
If you are using preemptible instances you have to specify shutdown script to gracefully reschedule build from preempted VM on another build agent like that.
For Linux instances:
#!/bin/bash
/opt/buildagent/bin/agent.sh stop forcesave your script in /etc/rc6.d
Notes:
- Make it executable: sudo chmod +x K99_script
- The script in rc6.d must be with no .sh extension
- The name of your script must begin with K99 to run at the right time.
- The scripts in this directory are executed in alphabetical order.
Apache 2.0
Please feel free to post feedback in the repository issues.