Monitor GitLab CI Scheduled Pipelines

The Problem

GitLab scheduled pipelines can fail silently if runners are unavailable, the pipeline configuration changes, or jobs timeout.

The Solution

Add a CronRabbit ping job at the end of your pipeline. If any preceding job fails, the ping doesn't execute and CronRabbit alerts you.

Integration

Add a monitor stage at the end of your pipeline with a simple curl command. Use when: on_success to ensure it only runs when all other stages pass.

Code Examples

GitLab CI with monitoring

Bash

# .gitlab-ci.yml
stages:
  - build
  - test
  - deploy
  - monitor

heartbeat:
  stage: monitor
  script:
    - curl -fsS -m 10 --retry 5 --retry-all-errors https://ping.cronrabbit.com/your-id
  when: on_success
  rules:
    - if: $CI_PIPELINE_SOURCE == "schedule"

Related Guides

DevOps & CI/CD

Monitor GitHub Actions Scheduled Workflows

Common Errors

Cron Job Not Running? How to Diagnose and Fix

DevOps & CI/CD

Monitor Cron Jobs Inside Docker Containers

Ready to Monitor Your Cron Jobs?

Create your free account and add your first monitor in under 5 minutes. No credit card required.