Manual pushes are fine to start, but coverage and trends only hold up when uploads happen automatically. This guide covers the canonical pattern for pushing scan results to Vibgrate Cloud from a CI pipeline.
Overview
In CI you cannot use an interactive browser login, so you authenticate with a DSN token and pass it with --dsn. The most efficient pattern is to scan and push in one step with vg scan --push, naming the repository so results land in the right place.
Prerequisites
- A DSN token generated with
vg dsn create(see Create a Data Source with vg dsn create). - The DSN stored as a masked secret in your CI provider.
Step-by-step
Add a step that scans and pushes, authenticating with the DSN and tagging the repository:
vg scan --push --dsn "$VIBGRATE_DSN" --repository-name org/my-service
If you prefer to keep scanning and uploading as separate stages — for example to gate on the scan before publishing results — run them in two steps:
vg scan
vg push --dsn "$VIBGRATE_DSN" --repository-name org/my-service
To try Vibgrate without installing it first, the no-install form is npx @vibgrate/cli scan.
Patterns
- Push on every merge to your main branch for fast trend updates.
- Add a scheduled nightly job so quiet repos still report; see Schedule Recurring Drift Reporting.
- Drive
--repository-namefrom your CI's repository variable so it is always correct.
Troubleshooting
Authentication failures usually mean a missing or stale DSN secret. See Troubleshooting Push and Authentication.
Related
Push Scan Results to Vibgrate Cloud and View Drift Trends on the Dashboard.