All templates

Automated TeamCity Broken Build Alerts

Every few minutes, WebRun checks TeamCity for build configurations that just failed on a main or release branch, creates a Trello card with the build log link, and messages the responsible developer on WhatsApp so a broken build gets picked up immediately.

Runs on WebRun · Strict Lockdown policy
Checks every 10 minutes, day and night WebRunorchestrates each step
1 TeamCity check for failed builds
2 Trello create the fix card
3 WhatsApp ping the build owner
In short

How do I get notified immediately when a TeamCity build breaks?

WebRun checks TeamCity every few minutes for build configurations that just failed on main or release branches. It creates a Trello card with the failing step and commit, then messages the developer responsible on WhatsApp, so a broken build gets a card and a direct ping within minutes instead of sitting unnoticed.

  • Broken builds get a card and a direct ping within minutes
  • The developer whose commit broke the build hears about it first
  • Main branch stays visible instead of quietly staying red

Built for Engineering teams · release engineers · DevOps leads · build engineers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens teamcity.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    TeamCity - check for failed builds
    • Open TeamCity and check the status of build configurations on main and release branches
    • Identify any build that just changed from success to failure
    • Note the failing step, the commit, and the last known good build

    Done when Every newly failed build is identified with its failing step and commit.

  3. 2
    Trello - create the fix card
    trello.com
    WebRun in Trello: create the fix card
    WebRun opens Trello to create the fix card.
    • Open the Build Fixes Trello board
    • Create a card titled with the build configuration name and the failing step
    • Attach the commit and the TeamCity build log link, and place it in the To Fix column

    Done when A Trello card exists for every newly broken build.

  4. 3
    WhatsApp - ping the build owner
    whatsapp.com
    WebRun in WhatsApp: ping the build owner
    WebRun opens WhatsApp to ping the build owner.
    • Message the developer whose commit triggered the build on WhatsApp
    • Include the build name, the failing step, and the Trello card link
    • Ask them to acknowledge or reassign the card

    Done when The responsible developer has been notified with a link to the fix card.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
teamcity.com
ScheduleRuns automatically on this cadence
Checks every 10 minutes, day and night
DeliveryHow each run's result reaches you
Build fix card · WhatsApp
OutputWhat each run produces - A Trello card per broken build and a direct WhatsApp ping to the developer whose commit broke it.
Alert
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will WebRun revert the commit or rerun the build itself?

No. It only reports the failure with a card and a message. Reverting a commit or rerunning the build is left to the developer.

Which branches does it watch?

By default it watches main and release branches, since those are the ones most likely to block other developers. You can add or remove branches in your run settings.

What happens if the same build keeps failing?

It will not create duplicate cards for a build that is already on the board and unresolved. It only pings again if the failure changes to a different step.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.