Automated CloudBees Build Agent Monitoring
Every hour, WebRun opens CloudBees, checks which build agents are connected and how many executors are free, reads the depth of the build queue, records the capacity picture in Google Sheets, and sends a Twilio text when jobs are queuing behind an agent that has dropped offline.
How do I get alerted when a CloudBees build agent goes offline?
WebRun checks CloudBees every hour, finds the build agents that have dropped offline, and reads how many jobs are queuing behind them. It logs the capacity picture in Google Sheets and texts the on-call engineer through Twilio when builds are actually blocked, so the team is not stuck waiting.
- Lost build capacity is caught within the hour
- Texts fire only when jobs are genuinely queuing behind an agent
- Repeat offenders show up in the hourly capacity history
Built for platform engineers · build engineers · DevOps teams · release 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 - check agents and queue depth
cloudbees.com
WebRun opens CloudBees to check agents and queue depth. - Open CloudBees and list the build agents attached to each controller
- Note which agents are offline or disconnected and when they were last seen
- Read how many executors are busy and how many are free
- Read the build queue and note how many jobs are waiting and for how long
- Match queued jobs to the labels the offline agents used to serve
Done when Every offline agent is identified and matched to the jobs now waiting for it.
-
2
Google Sheets - log the hourly capacity
google.com
WebRun opens Google Sheets to log the hourly capacity. - Append an hourly row to your capacity sheet
- Record the agent count online, executors free, queue depth, and longest wait
- Add a column naming any agent that went offline this hour
- Keep the history so a pattern of daily drop-outs becomes visible
Done when This hour's capacity snapshot is a row in the Google Sheet.
-
3
Twilio - text when the queue backs up
twilio.com
WebRun opens Twilio to text when the queue backs up. - Send a text to the on-call engineer when an agent is offline and jobs are queuing behind it
- Name the agent, the controller, and how many jobs are waiting
- Hold the text if the queue is empty, since a quiet agent blocks nobody
- Send at most one text per agent per incident so nobody is paged repeatedly
Done when The on-call engineer is texted about lost capacity that is actually blocking builds.
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 restart agents or cancel queued builds?
No. WebRun reads the controller and reports what it sees. Restarting an agent, cancelling a build, or draining a queue stays with your engineers, because those actions change what is running in your pipeline.
Who receives the text and when?
The on-call number you set, and only when an agent is offline and jobs are actually queuing behind it. A quiet agent with an empty queue blocks nobody, so it does not page anyone.
How is this different from pipeline failure escalation?
Failure escalation reacts to builds that ran and failed. This run watches the capacity underneath them, so lost executors are caught while jobs are still waiting rather than after a build times out.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.