Automated Semaphore CI Build Time Tracking
Every evening, WebRun opens Semaphore CI, pulls the day's pipeline runs across every project, exports the average build duration and pass and fail counts to a Google Sheet so the trend builds over time, and emails the team a short summary only when the average build time has crept up notably from the recent baseline.
How do I catch my CI build times creeping up over time?
WebRun pulls your Semaphore CI pipeline results every evening, exporting the day's average build duration and pass rate to a Google Sheet with a rolling baseline. It emails the team only when build time creeps up notably, so slow builds get caught early instead of becoming the new normal unnoticed.
- Build time creep gets caught early instead of becoming the norm
- The slowest projects are visible in the trend, not just the average
- Routine days stay quiet since the email only fires on a real slowdown
Built for DevOps teams · platform engineers · engineering managers · release engineers
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
semaphoreci.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Semaphore CI - pull the day's pipeline durations
- Open Semaphore CI and pull today's pipeline runs across all projects
- Calculate the average build duration and total pass and fail counts
- Compare today's average duration against the rolling baseline
Done when Today's pipeline runs are totaled with average duration and pass and fail counts.
-
2
Google Sheets - export build times to a sheet
WebRun opens Google Sheets to export build times to a sheet. - Add today's totals as a new row in the build time tracker
- Record the average duration and the rolling baseline
- Keep prior days in place so the trend is visible
Done when Today's row is logged in the sheet with the rolling baseline updated.
-
3
Gmail - email a summary if times creep up
WebRun opens Gmail to email a summary if times creep up. - Draft a short internal email only when today's average build time is notably above the baseline
- Name the projects contributing most to the slowdown
- Skip the email entirely on a normal day
Done when The team has an email only on days build time crept up notably.
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 change any pipeline configuration to speed things up?
No. WebRun only reads and logs build durations. Optimizing a pipeline is always done by an engineer.
Do I get an email every day?
No. The sheet is updated daily, but the email only goes out when the average build time is notably above the rolling baseline.
Can I see which projects are the slowest?
Yes. Every row records which projects contributed most to a slowdown, so patterns show up in the sheet over time.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.