TeamCity Minimal Agent

The TeamCity Minimal Agent is a lightweight container image that runs build and test tasks for a JetBrains TeamCity server.

  • Development
  • Tools & Utilities
The TeamCity Minimal Agent is a lightweight container image that runs build and test tasks for a JetBrains TeamCity server. It ships only the essential tools an agent needs to check out code and execute build steps, so it starts quickly and uses fewer resources than full agent images. It suits teams that want a small, fast Docker build worker. Note that JetBrains has deprecated this image and no longer supports it; the repository README recommends the maintained teamcity-docker-images project instead.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?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). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

34/100 Low

Maintained
0last commit 1373 days ago
Popular
2825 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
95500 MB minimum RAM, runs on ARM
Security check
75no serious findings
GitHub stars
25
Open issues
10
Last commit
2023-02-17
License
Apache-2.0
Activity
stale

Checked 3 days ago - source: GitHub (JetBrains/teamcity-docker-minimal-agent)

Resources & Compatibility

Minimum requirements: 500 MB RAM. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Deprecation notice This image is deprecated: the repository README states it is no longer supported and points to the maintained teamcity-docker-images project as the replacement. It can still be pulled from Docker Hub as jetbrains/teamcity-minimal-agent. source

Fetched 41 days ago - each note links to its source

Alternatives (7)

  • 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.
  • Codeship - Codeship is a hosted Continuous Delivery Service that integrates with GitHub and Bitbucket.
  • 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.
  • gocd - GoCD is an open-source continuous delivery server that automates and visualizes build, test, and release workflows for software teams.
  • teamcity - TeamCity is JetBrains' server-based continuous integration and continuous delivery (CI/CD) system for building, testing, and deploying soft…

Checked 40 days ago - source: AlternativeTo

Common questions

How can I customize the teamcity-minimal-agent Docker image for my own agent?

You can log into the running container, make the needed changes, commit the container to a new image, and update the environment variables in the agent config folder.

Why does a TeamCity Docker agent sometimes appear as a new unique build agent every time it runs?

This is an agent identity or naming issue: the containerized agent can be treated as a new, unique build agent on each start.

Why does a build command work locally but fail on the TeamCity agent?

Make sure the command works on the agent machine under the same user and environment as the TeamCity agent; if necessary, run the agent under a different user or tweak its environment.

Can TeamCity runs be isolated by using containers?

Yes, one option is to run builds in containers. TeamCity can also be configured to set an image.

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

Community

Collected 48 days ago - public community threads