Automated Bitbucket Build Failure Digest
Every morning, WebRun opens Bitbucket, collects the Pipelines runs that failed overnight across your repositories, captures the repo, branch, commit author, and failing step, records them on your engineering Notion page, and messages the on-call engineer the summary on WhatsApp.
How do I get a daily summary of failed CI builds?
WebRun opens Bitbucket every morning and collects the Pipelines runs that failed overnight across your repositories, capturing the repo, branch, commit author, and failing step. It records them on your Notion build health page and messages the on-call engineer a summary on WhatsApp, so broken builds have an owner by 8am.
- Main-branch breakages are named and owned before standup
- Repeat failures are visible instead of blending into the noise
- Notion keeps a running record so build health is measurable
Built for engineering teams · DevOps engineers · platform teams · engineering managers
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
bitbucket.org/account/signinin a real browser with your saved login - no setup, no API keys. -
1
Bitbucket - collect the overnight build failures
bitbucket.org
WebRun opens Bitbucket to collect the overnight build failures. - Open Bitbucket and go to Pipelines for each repository you track
- Filter to runs since the last check with a failed or stopped result
- Capture the repository, the branch, the commit author, the pipeline step that failed, and the error line
- Note whether the same pipeline also failed on the previous run
Done when Every failed pipeline run since the last check is captured with its author.
-
2
Notion - record the failure list
notion.so
WebRun opens Notion to record the failure list. - Open your engineering build health page in Notion
- Add today's entry with one line per failed run, linked back to the pipeline
- Mark failures on the main branch separately from feature branches
- Keep past days so the failure rate is visible over time
Done when Today's failures are recorded on the Notion build health page.
-
3
WhatsApp - message the on-call engineer
whatsapp.com
WebRun opens WhatsApp to message the on-call engineer. - Message the engineering WhatsApp group with the overnight summary
- Lead with main-branch failures, then repeated failures, then everything else
- Name the commit author next to each so the fix has an obvious owner
- Say plainly when every pipeline passed overnight
Done when The on-call engineer has this morning's failure summary.
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 rerun a pipeline or merge anything?
No. WebRun only reads Bitbucket. It never reruns a pipeline, merges a pull request, pushes a commit, or changes a branch permission. Every action on the repo stays a human decision.
Can I limit it to the main branch?
Yes. Pick the repositories and branches you care about when you turn it on. Many teams report only main and release branches, and leave feature-branch noise out.
Does it read the full build logs?
It reads enough of the failing step to quote the error line in the digest. The full log stays in Bitbucket, linked from the Notion entry for whoever picks up the fix.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.