← Directory

TeamCity Build Agent

JetBrains TeamCity Build Agent is an official Docker image that runs a TeamCity build agent inside a container.

  • Other
  • Productivity
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
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on GitHub

Health score

29/100 Low

Maintained
No data
Popular
No data
Easy to install
201 install platform, Docker image
Light to run
404 GB minimum RAM, runs on ARM

Based on 2 of 4 factors.

How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today, links checked 9 days ago

GitHub stars
77
Open issues
19
Last commit
2023-02-17
License
Apache-2.0
Activity
stale

Checked today - source: GitHub (JetBrains/teamcity-docker-agent)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 2 CPU core(s), 20 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 9 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Requires a running TeamCity server A TeamCity build agent listens for commands from a TeamCity server and starts the actual build processes, so you need a running TeamCity server (JetBrains ships a separate teamcity-server image) and must point this agent at it before any builds will run. source

Fetched today - each note links to its source

Alternatives (5)

  • 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…

Checked 6 days ago - source: AlternativeTo

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.

Answers sourced from stackoverflow.com, www.jetbrains.com, www.reddit.com, www.reddit.com

Community

Collected 4 days ago - public community threads