# TeamCity Build Agent

TeamCity Build Agent is a self-hosted other app. JetBrains TeamCity Build Agent is an official Docker image that runs a TeamCity build agent inside a container. It is open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/444/teamcity-build-agent

## Description

JetBrains TeamCity Build Agent is an official Docker image that runs a TeamCity build agent inside a container. The agent connects to a TeamCity server and starts the actual build processes, so you can scale builds across homelab or cloud machines. It is based on the lighter teamcity-minimal-agent image but adds client-side Git and Mercurial checkout, extra bundled build tools, and Docker-in-Docker on Linux. The original teamcity-docker-agent repository is deprecated; the image is now maintained under JetBrains' teamcity-docker-images project.

## Platform availability

Available on 1 of 6 install platforms: Unraid.

## Health score

29/100 (Low), based on 2 of 4 factors.
- Easy to install: 20 (1 install platform, Docker image)
- Light to run: 40 (4 GB minimum RAM, runs on ARM)

## Links

- Unraid: https://ca.unraid.net/apps/teamcity-buildagent-05ikbiu0y1aalu?q=TeamCity-BuildAgent
- GitHub: https://github.com/JetBrains/teamcity-docker-agent

## Common questions

### What are the TeamCity self-hosted licensing limits without a commercial license?

Without a commercial license, TeamCity is limited to 100 build configs and about 3 build agents.

### How should I handle HTTPS and default ports for TeamCity and the build agent?

TeamCity generally serves HTTP on port 8111, and the agent commonly uses port 8112. Use a reverse proxy such as Caddy, nginx, or HAProxy for HTTPS instead of having TeamCity serve HTTPS directly.

### Why can a TeamCity build agent fail to create a build temp directory when added to a build pool?

The agent may fail to create the build temp directory because it lacks permission to create that directory after being added to the pool.

### What should I try if a TeamCity agent installed as a Windows service does not behave as expected?

Try running the TeamCity agent under a regular user with administrative permissions from the command line.

## Alternatives

- Azure DevOps: Continuous Delivery Services for teams to share code, track work, and ship software – for any language, all in a single package.
- CircleCI: CircleCI provides development teams the confidence to build, test, and deploy—quickly and consistently—across numerous platforms.
- Jenkins: Jenkins is a fork of Hudson and is a continuous build system for software projects.
- Octopus Deploy: Octopus Deploy is a user-friendly release management system for professional .NET developers.
- Travis CI: Travis CI is a leading provider of continuous integration and delivery services and empowers software development teams to test and deploy…

---
Source: Our Local Host (https://ourlocalhost.com/app/444/teamcity-build-agent), the self-hosted and open-source app directory.