All integrationsCode Repositories

TeamCity

Run and follow your TeamCity builds: trigger builds with a branch and parameters, wait for them, read their status, log, problems, tests and artifacts, cancel, pin, tag and comment on them, pause configurations, manage agents, and start a workflow when a build fails, finishes or starts, or an agent disconnects.

actions
24
triggers
4

Triggers

Start a workflow when something happens in TeamCity.

  • Build failedRuns when a TeamCity build fails, of every configuration, one or a project's, on any branch or one, with TeamCity's summary of why. Cancelled builds and builds that failed before the workflow was turned on don't start it.
  • Build finishedRuns when a TeamCity build finishes, successful or failed, or only with the status you choose. Cancelled builds don't start it.
  • Build startedRuns when a TeamCity build starts on an agent, of every configuration, one or a project's, on any branch or one.
  • Agent disconnectedRuns when an authorized build agent disconnects from TeamCity, such as when its machine goes down. It runs again the next time, once the agent is back.

Actions

Steps a workflow can run in TeamCity.

  • List projectsList TeamCity projects by name, with the project each is in.
  • Get projectGet a TeamCity project with its build configurations and subprojects.
  • List build configurationsList build configurations, of every project or one (its subprojects too), with whether each is paused.
  • Get build configurationGet a build configuration: whether it's paused, its parameters (the ones Trigger build can set), its steps and triggers, and its latest finished build.
  • Pause build configurationPause a build configuration, so its triggers start no builds until it's activated. Builds already queued or running carry on, and it can still be run by hand.
  • Activate build configurationActivate a paused build configuration, so its triggers start builds again.
  • Trigger buildPut a build of a configuration in the queue, as TeamCity's Run button does, on a branch and with parameters and a comment. It doesn't wait for the build: follow it with Wait for build.
  • Wait for buildWait until a build finishes, checking every minute without holding the workflow, then get it with its status. If it's still queued or running when the time is up, the step fails; the build carries on.
  • Get buildGet a build: whether it's queued, running or finished, its status and TeamCity's summary of it, its branch, the changes it builds, who started it, and its test counts.
  • List buildsList builds, the latest first, of every configuration, one or a project's, by branch, status, state, tag and time.
  • Cancel buildCancel a build: one in the queue is taken out of it, and one that's running is stopped. A build that has finished is left as it is.
  • Pin buildPin a finished build, so TeamCity's clean-up never deletes it or its artifacts, such as a release.
  • Unpin buildUnpin a build, so clean-up can delete it again under the project's rules.
  • Tag buildAdd tags to a build and take others off, keeping the rest, such as release or deployed-to-staging.
  • Comment on buildSet a build's comment, which TeamCity shows with it, replacing the one it had. Leave the comment blank to remove it.
  • Get build logGet a build's log, its last lines, as TeamCity's Build Log tab shows them, or only the lines that mention an error or failure.
  • Get build problemsGet why a build failed: the problems TeamCity reported, such as a step's exit code, failed tests or a compilation error.
  • Get build testsGet a build's failed tests, with each failure's message, or all its tests.
  • List build artifactsList the files a build published as artifacts, in one folder or all of them, each with its download address.
  • Get artifactGet one of a build's artifacts: its size and download addresses, and its text when asked, such as a report a later step reads.
  • List queued buildsList the builds waiting in TeamCity's queue, the next to start first, with why each is waiting.
  • List agentsList build agents, with whether each is connected, authorized and enabled, its pool and the build it's running.
  • Enable agentEnable a build agent, so it takes builds again.
  • Disable agentDisable a build agent, such as for maintenance: it finishes the build it's running and takes no more until enabled.

Automate TeamCity with Lodol.

Connect TeamCity, then hand Lodol the job in Slack, Claude or ChatGPT.

Free plan, no credit card