The template allows deploying aTeamCity server and agent in Azure cloud. It creates a MySQL database, a virtual machine with CoreOS and starts TeamCity in a docker container.

Note: You need to deploy it into a dedicated resource group.

Allows specifying the required version of TeamCity for deployment.

List of pre-configured installation types:

Note: Pricing for Azure virtual machines and MySQL database.

Allows specifying username to login to a virtual machine where TeamCity is running.

Allows specifying a publish ssh key for the user used to connect to virtial machine with TeamCity.

Allows specifying password for the MySQL database.

After deployment you will be able to connect to the teamcity virtual machine via SSH. In CoreOS TeamCity works as the following systemd service:

• teamcity-server.service - launches TeamCity server.
• teamcity-agent.service - launches TeamCity agent.
• teamcity-update.service - check for TeamCity version updates.

The template installs the following Azure integrations in TeamCity:

• Azure Cloud Agents - allows to scale the pool of TeamCity build agents by leveraging Azure virtual machines.
• Azure Artifacts Storage - allows to store build artifacts in Azure Cloud Storage Blobs.
• Azure Active Directory - allows to use Azure AD authentication in TeamCity.

Note: TeamCity server exposes HTTP endpoint, so please make sure to enable HTTPS endpoint for virtual machine for production usage.

During deployment, a teamcity virtual machine will be tagged with the teamcity-version tag. To change the TeamCity version, you need to update the tag value and restart the teamcity-server.service and teamcity-agent.service systemd services or the virtual machine.

Please feel free to send a PR or file an issue in the TeamCity issue tracker.