OpenParable
Skip to content
← Back to skills

Teamcity CLI

DevOps & Security
teamcity-cli

Teamcity CLI is an Agent Skill for devops & security published in the JetBrains/MPS repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when working with TeamCity CI/CD or when user provides a TeamCity build URL. Use `teamcity` CLI for builds, logs, jobs, queues, agents, and pipelines.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/JetBrains/MPS/blob/HEAD/.claude/skills/teamcity-cli/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/teamcity-cli, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

TeamCity CLI (teamcity)

teamcity auth status                    # Check authentication
teamcity run list --status failure      # Find failed builds
teamcity run log <id> --failed --raw    # Full failure diagnostics

Do not guess flags or syntax. Use the Command Reference or teamcity <command> --help. Builds are runs (teamcity run), build configurations are jobs (teamcity job). Never use --count — use --limit (or -n).

Gotchas

  • Composite builds have empty logs — drill into child builds for the actual failure.
  • Build chains fail bottom-up — the deepest failed dependency is the root cause, not the top-level build. Use teamcity run tree <id>.
  • --local-changes excludes Kotlin DSL — push .teamcity/ changes before running.
  • Always use --raw for logs and dump to a temp file. Always use --watch when starting builds.
  • VCS triggers aren't always configured — after pushing a fix, you may need to start builds manually.
  • pipeline push does not validate — always run teamcity pipeline validate first.

Core Commands

AreaCommands
Buildsrun list, view, start, watch, log, cancel, restart, tests, changes, tree
Artifactsrun artifacts, run download
Metadatarun pin/unpin, run tag/untag, run comment
Jobsjob list, view, tree, pause/resume, param list/get/set/delete
Projectsproject list, view, tree, param, token put/get, settings export/status/validate
Queuequeue list, approve, remove, top
Agentsagent list, view, enable/disable, authorize/deauthorize, exec, term, reboot, move
Poolspool list, view, link/unlink
Pipelinespipeline list, view, create, validate, pull, push, delete
APIteamcity api <endpoint> — raw REST API access

Quick Workflows

See Workflows for full details on each.

Investigate failure: teamcity run list --status failure → teamcity run log <id> --failed --raw → teamcity run tests <id> --failed Debug build chain: teamcity run tree <run-id> → find deepest failed child → investigate that build Fix build failure: diagnose → classify → fix (code: --local-changes, DSL: settings validate, pipeline: pipeline validate) → push Monitor until green: start → watch → fix if failed → push → watch new build → repeat (max 3 attempts) Pipeline: teamcity pipeline create <name> -p <project> / teamcity pipeline validate [file] / teamcity pipeline pull <pipeline-id> → edit → teamcity pipeline push <pipeline-id> [file]

References