← ClaudeAtlas

teamcity-clilisted

Use when working with TeamCity CI/CD or when a user provides a TeamCity build URL — drives the `teamcity` CLI for builds, logs, jobs, queues, agents, pools, projects, and pipelines.
JetBrains/teamcity-cli · ★ 89 · DevOps & Infrastructure · score 85
Install: claude install-skill JetBrains/teamcity-cli
# TeamCity CLI (`teamcity`) ## Quick Start ```bash 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](references/commands.md) 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** — deepest failed dependency is the root cause. Use `teamcity run tree <id>`. - **`--local-changes` excludes Kotlin DSL** — push `.teamcity/` changes before running. - **`TEAMCITY_URL` alone bypasses stored auth** — set both `TEAMCITY_URL` and `TEAMCITY_TOKEN`, or leave unset. - **Logs**: use `--raw` and dump to a temp file. **Builds**: use `--watch` when starting them. - **VCS triggers aren't always wired up** — after pushing a fix you may need to start builds manually. - **`pipeline push` does not validate** — always `teamcity pipeline validate` first. - **GitHub VCS roots: use a GitHub App connection.** Never paste a PAT via `--auth password`. See [workflows](references/workflows.md). ## Core Commands | Area | Commands | |-----------|------------------