Automated CloudBees Pipeline Failure Escalation
Every hour, WebRun opens CloudBees, checks pipeline runs on release branches for a failure, posts each new failure to Slack with the branch and failing stage, and separately pages the team's Telegram channel when the same pipeline fails twice in a row so a real blocker gets attention instead of looking like one more routine failure.
How do I escalate repeated CloudBees pipeline failures automatically?
WebRun checks CloudBees every hour for pipeline failures on release branches, posting each new failure to Slack with its branch and failing stage. When the same pipeline fails twice in a row, it also pages the team's Telegram channel, so a genuine blocker stands out from routine, one off failures.
- Repeated failures get paged instead of blending into routine noise
- Release branch problems surface within the hour
- The team can tell a flaky step from a real blocker at a glance
Built for DevOps teams · release engineers · platform engineers · software engineering teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.cloudbees.comin a real browser with your saved login - no setup, no API keys. -
1
CloudBees - check pipeline runs on release branches
- Open CloudBees and check the latest run on each release branch pipeline
- Capture the branch, stage, and failure reason for anything that failed
- Track whether the same pipeline also failed on its prior run
Done when Every newly failed pipeline run is listed with its branch and whether it's a repeat failure.
-
2
Slack - post the failure to the team
slack.com
WebRun opens Slack to post the failure to the team. - Post each new failure to the release channel with its branch and failing stage
- Note whether it's the pipeline's first failure or a repeat
- Skip failures already posted this hour
Done when The release channel has a post for every newly failed pipeline run.
-
3
Telegram - page after repeated failures
telegram.org
WebRun opens Telegram to page after repeated failures. - Send a page only when a pipeline fails for the second run in a row
- Name the branch and the stage that keeps failing
- Skip this step for a first time failure
Done when Every pipeline that failed twice in a row has a page in Telegram.
How is each run configured?
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.
Every action is checked against this policy before it runs.
Questions, answered
Will it retry the pipeline or fix the code?
No. WebRun only reports the failure. Retrying the pipeline or fixing the code is always done by an engineer.
Why escalate only on the second failure?
A single failure is often a flaky step. Two in a row is a stronger signal that something needs real attention, so that's what triggers the Telegram page.
Does this cover all branches?
It focuses on release branches specifically, since those are the ones that block a release if they stay broken.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.