Docs › Jenkins scheduled builds with RunVouch

Jenkins scheduled builds with RunVouch

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 RunVouch detects

Need a key? Get a free key · Stuck? contact