Eric Borchardt

TeamCity build steps cannot directly change the in-memory environment of another step. To pass a newly computed value to later steps, emit a setParameter TeamCity Service Message to standard output...

Problem A vulnerability scanner (for example, Tenable, Nessus, or Qualys) reports an outdated, vulnerable TeamCity version on a Windows server. On the same server, the TeamCity web UI shows a newer...

Problem A build configuration runs on an older VCS revision than a build of the same configuration that already finished, so TeamCity marks it a History build (it shows History in the Changes colum...

Symptoms After the CVE-2026-63077 security patch is installed, or after upgrading to TeamCity 2026.1.3 or 2025.11.7, unauthorized build agents appear in the agents list, typically named scan-<rando...

Background A TeamCity test or staging server is almost always a copy of a production server: the same projects, build configurations, database, and Data Directory. A direct copy keeps every externa...

Question How can the TeamCity REST API be reached from outside the server machine over HTTPS, when it is currently available only internally (for example, at http://localhost:8111)? Answer The REST...

Symptoms On a TeamCity build agent, the Git VCS uses HTTPS authentication and the agent has the Git credential cache helper configured: [credential] helper = cache --timeout=3600 After a TeamC...

Note This article covers self-hosted TeamCity On-Premises and is not related to the hosted TeamCity Cloud offering. Question How should a self-hosted TeamCity High Availability (multinode) setup be...

Symptoms A build configuration monitors pull request or feature branches with a VCS trigger, and the default branch is excluded from triggering so that builds run on pull requests only. A typical s...

Question A multinode (high-availability) TeamCity On-Premises setup shares a single Data Directory and one external database across all server nodes. The Data Directory usually lives on a network f...