Automated CloudBees Build Health Reports
Every Monday, WebRun opens CloudBees, reads last week's build and pipeline history for the jobs you track, works out success rate, average duration, and which jobs failed most, writes the whole report into a Notion engineering page, and sends the headline numbers to your team WhatsApp group.
How do I get a weekly report on CI build success rates?
WebRun writes your CloudBees build health report every Monday. It reads last week's runs for the jobs you track, works out success rate, average duration, and the jobs that failed repeatedly, publishes the full table to a Notion page, and sends the headline numbers to your team WhatsApp group.
- Build success rate and duration trends are written down every week, not guessed at
- Repeat failing jobs are named with the stage that breaks them
- The team gets the headline on their phone with the full report one link away
Built for platform engineering teams · DevOps leads · release managers · 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
www.cloudbees.comin a real browser with your saved login - no setup, no API keys. -
1
CloudBees - read last week's builds
cloudbees.com
WebRun opens CloudBees to read last week's builds. - Open CloudBees and go to the pipelines and jobs you track
- For the last 7 days record total runs, successes, and failures per job
- Capture average and longest build duration per job, and how each compares with the week before
- List the jobs that failed more than once and note whether the failures repeat on the same stage
Done when Every tracked job has last week's run counts, durations, and failure pattern.
-
2
Notion - write the health report
notion.so
WebRun opens Notion to write the health report. - Create this week's page in the engineering health database in Notion
- Write a table of jobs with runs, success rate, average duration, and the change on last week
- Add a short section on the jobs that failed repeatedly, naming the stage that broke
- Link the page to last week's entry so the trend is one click away
Done when This week's health report page exists in Notion with the full table.
-
3
WhatsApp - send the headline numbers
whatsapp.com
WebRun opens WhatsApp to send the headline numbers. - Send the headline numbers to your internal engineering WhatsApp group
- Include overall success rate, the slowest job, and the worst repeat offender
- Add the link to the full Notion page
- Keep it to a few lines so it reads on a phone
Done when The team has this week's headline build numbers in WhatsApp.
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 start, stop, or retry any builds?
No. WebRun only reads build history in CloudBees. It never triggers a job, cancels a run, retries a failure, or changes a pipeline definition, so nothing is deployed or rebuilt because of this workflow.
Does it copy build logs anywhere?
No. It records run counts, durations, statuses, and the stage name where a job failed. Full logs and any secrets inside them stay in CloudBees and are never written to Notion or WhatsApp.
Can I limit it to certain pipelines?
Yes. Name the jobs or folders you care about and the report covers only those, which keeps a large controller from producing an unreadable table.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.