Glossary
This glossary defines the key terms used in TeamCity CLI and maps them to their TeamCity equivalents.
Run
A single execution of a build configuration. Equivalent to build in the TeamCity web interface.
Job
A set of instructions for running a build. Equivalent to build configuration in the TeamCity web interface.
Project
A collection of build configurations (jobs) with an associated name and description. Projects can be nested to form a hierarchy.
Build Queue
A list of builds waiting to be assigned to an available agent. Builds in the queue are distributed to compatible agents as resources become available. The queue can be reordered manually.
Build Agent
A piece of software that executes builds. Agents are installed on separate machines and are assigned builds based on their compatibility with build configurations.
Agent Pool
A named group of build agents. Projects can be linked to pools to control which agents run their builds.
Change
A modification to source code detected by TeamCity. A change is considered pending when it has been committed to the VCS but not yet included in a build.
Personal Build
A build initiated by a developer to test local changes without affecting the main build history. In TeamCity CLI, personal builds are triggered using the --local-changes flag.
Alias
A custom command shortcut that expands into a full teamcity command. Aliases support positional arguments and shell expressions.
Skill
A bundled configuration file that teaches AI coding agents (Claude Code, Cursor, and others) how to use TeamCity CLI. Skills follow the Agent Skills specification.
Terminology mapping
CLI term | TeamCity term |
|---|---|
| build |
| build configuration |
| project |
| build queue |
| build agent |
| agent pool |