Docs › Jenkins scheduled build monitoring with RunVouch
Jenkins scheduled build monitoring with RunVouch
Jenkins scheduled build monitoring for what a red ball cannot show: Jenkins tells you about red builds. It does not tell you a job has not been triggered for a week because the trigger was edited away, or that a green build's script exited 0 with an empty report.
How it runs on Jenkins
In a Pipeline sh step or a freestyle shell build step, on the agent that runs the job.
Store the key
Store the key as a Secret text credential and bind it with withCredentials([string(credentialsId: 'runvouch', variable: 'RUNVOUCH_KEY')]).
Wrap the job
pipeline {
agent any
triggers { cron('H 2 * * *') }
stages {
stage('report') {
steps {
withCredentials([string(credentialsId: 'runvouch', variable: 'RUNVOUCH_KEY')]) {
sh 'rv run nightly-report --evidence-file out/report.html -- python3 report.py'
}
}
}
}
}rv fails open: if RunVouch is unreachable the job still runs and you get one warning line.
Register the cadence and caps
rv agent nightly-report --cadence 24h --grace 30m --max-runtime 1h --evidence --cap-run-cost 2
Register the agent once, from anywhere with the key. Cadence is what turns a schedule that stopped into an alert; --evidence makes a run without evidence a failure; the caps pause the agent when it overspends.
What goes silent on Jenkins
- A disabled job or a removed trigger produces no notification; MISSED does.
- Post-build e-mail fires on failure or unstable, never on "passed, produced nothing".
- Queued builds that wait for an executor for hours are not late to Jenkins; STALLED and MISSED are measured against your cadence, not the queue.
What Jenkins does not tell you
Jenkins notifies on build result: failure, unstable, back to normal. A job that is disabled, whose triggers { cron() } block was removed in a Jenkinsfile change, or whose agent label no longer matches any node, sits in the queue or never enters it, and no build result is produced to notify about. Console output is kept per build; a build that printed nothing and exited 0 is a blue ball.
What RunVouch detects
| Alert | What it means here |
|---|---|
| MISSED | cadence plus grace passed and no run started |
| FAILED | non-zero exit or a reported failure, with the stderr excerpt |
| NO_EVIDENCE | the run said ok but the file, URL or assertion you required is missing |
| STALLED | a run started and never ended within max runtime |
| RETRY_STORM | the same tool called with identical input many times in one run |
| BUDGET_RUN / BUDGET_DAY | cost cap crossed; the agent is paused until you resume it |
| DRIFT | duration or output size far off its 7-run baseline |
Set up in two minutes
- Get a free key (3 agents, no card) and store it where this page says.
- wrap the job: copy the snippet above into the scheduled job.
- Register the cadence once:
rv agent nightly-report --cadence 24h --grace 30m --evidence, or let the first run create the agent and set the cadence on the dashboard. - Send one test alert:
curl -X POST https://api.runvouch.com/v1/settings/test-alert -H "X-API-Key: $RUNVOUCH_KEY". The next missed, failed or empty run reaches the same channels.
Also running schedulers?
Heroku Scheduler. Claude Code scheduled tasks. OpenClaw automations and heartbeat. GitHub Actions schedule. The full list of runtimes is on integrations, and the same agent can report from several of them: one job, one cadence, wherever it happens to run.
Need a key? Get a free key · Stuck? contact