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. - **Select a server per command with `TEAMCITY_URL`** — `TEAMCITY_URL=https://cli.teamcity.com teamcity run list` uses stored credentials for that server; set `TEAMCITY_TOKEN` to override them. - **Read-only mode blocks remote shells** — `TEAMCITY_RO=1` or per-server `ro: true` rejects `agent exec` and `agent term` before connecting. - **Multi-root runs**: repeat `--revision ROOT=SHA[@BRANCH]`; `ROOT=@BRANCH` uses a fetched branch head. Bare SHA pins every root. - **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 v...