Drift does not stand still — new releases of your dependencies appear constantly. To keep Vibgrate Cloud trends meaningful, results need to arrive on a regular cadence. This guide shows how to set up recurring drift reporting.
Overview
Vibgrate's CLI is designed to be run unattended. By scheduling vg scan --push to run on a fixed cadence (for example nightly, or on every merge), you keep your DriftScore current and your trend lines continuous without manual effort.
Prerequisites
- A scheduler — most teams use their CI provider's scheduled pipeline feature.
- A DSN for non-interactive auth (see Create a Data Source with vg dsn create).
Step-by-step
In a scheduled CI job, scan and push in one step, authenticating with a DSN and naming the repository:
vg scan --push --dsn "$VIBGRATE_DSN" --repository-name org/my-service
Configure the job to run on the cadence you want — nightly is a common baseline, with an additional push on every merge to your main branch for fast feedback.
Choosing a cadence
- On every merge: catches drift the moment it is introduced; best for active repos.
- Nightly: low-noise baseline that keeps trends fresh even for quiet repos.
- Weekly: minimum useful cadence for archival or slow-moving services.
A blend works well: push on merge for fast feedback, and run a nightly scheduled job so a repo never goes dark in the dashboard.
Related
Push from CI Pipelines for the full CI patterns, View Drift Trends on the Dashboard to read the result, and Schedule-friendly executive summaries.