Docs › GitLab CI scheduled pipelines with RunVouch

GitLab CI scheduled pipelines with RunVouch

Pipeline schedules run as the user who created them. When that user leaves or the schedule is deactivated the pipeline silently stops, and a job that passes is not a job that did the work.

How it runs on GitLab CI scheduled pipelines

Inside the job's script:. The runner image needs Python 3 (pip install runvouch) or the single rv file fetched with curl.

Store the key

Add RUNVOUCH_KEY as a masked, protected CI/CD variable (Settings, CI/CD, Variables).

Wrap the job

nightly-report:
  rules:
    - if: $CI_PIPELINE_SOURCE == "schedule"
  script:
    - pip install -q runvouch
    - rv run nightly-report --evidence-file public/report.html -- python report.py
  artifacts:
    paths: [public/report.html]

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 GitLab CI scheduled pipelines

• A deactivated schedule, or one whose owner lost access to the project, stops without a notification. MISSED covers it.
• Pipeline notifications fire on failure, not on "passed but wrote nothing"; --evidence-file does.
• Retried jobs (retry:) can run an LLM step several times; the retry-storm and per-run cost cap see the repeats.

What RunVouch detects

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