This recipe uploads CI scan results to Vibgrate Cloud so the whole team can see drift trends in one place. It is for teams that want centralized, historical visibility beyond a single build log.
What pushing does
Pushing sends the scan result to your Vibgrate Cloud workspace, where it is stored and plotted over time. The dashboard at dash.vibgrate.com shows per-repository and per-branch DriftScore trends.
Authenticating CI
CI runners are non-interactive, so they authenticate with a DSN token instead of a browser login. Generate one with:
vg dsn create
Store the resulting token as a secret in your CI provider. Never commit it or print it in logs.
Pushing from a job
With the DSN available to the job as a secret, run a scan with --push:
npx @vibgrate/cli scan --push
Post-install:
vg scan --push
The scan runs as usual and then uploads the result to Vibgrate Cloud.
Combining push with a gate
You can push and gate in the same run so the build records the result and still fails on regressions:
vg scan --push --fail-on error
Where to push from
A common pattern is to push from main-branch and scheduled runs to keep a clean trend, while PR runs only gate. See Schedule nightly Vibgrate scans in CI.
Related
- Gate pull requests on a drift budget for PR enforcement.
- Monorepo matrix scans to push per-package results.