Failing a Scan on Finding Severity
Turn a Vibgrate scan into a quality gate with --fail-on. Learn how to fail the build when findings reach a chosen severity so risky drift blocks merges.
CI Integration articles for the Vibgrate CLI.
Turn a Vibgrate scan into a quality gate with --fail-on. Learn how to fail the build when findings reach a chosen severity so risky drift blocks merges.
Keep CI logs clean with the --quiet flag. Learn how quiet mode suppresses extra console output so pipelines show only what matters and exit codes drive decisions.
Push scan results from automated pipelines without an interactive browser by using a DSN token, so vg push works headlessly in CI.
A guide to running vg status in continuous integration to keep the committed code map fresh — detecting staleness, gating on freshness, and rebuilding when the graph drifts from the working tree.
Add Vibgrate drift scanning to a Jenkins declarative pipeline. Learn how to install the CLI on an agent, run a scan, fail the build on regressions, and archive the report artifact.
Wire the Vibgrate CLI into a CircleCI job. Learn how to run a scan in a Node executor, set a quality gate, and persist the report as a build artifact.
Configure bitbucket-pipelines.yml to run Vibgrate drift scans on every push and pull request. Learn how to set a quality gate and keep the report as an artifact.
Set up .travis.yml to run Vibgrate drift scans in a Node environment. Learn how to fail builds on regressions and produce a report artifact.
Add a Vibgrate drift scan step to a Drone pipeline using a Node container. Learn how to apply a quality gate and surface the DriftScore on every build.
Add a Vibgrate drift scan step to a Buildkite pipeline running on self-hosted agents. Learn how to gate builds and upload the report as a Buildkite artifact.
Add a command-line build step that runs Vibgrate drift scanning in TeamCity. Learn how to fail builds on regressions and keep the report as a build artifact.
Add a Run step to a Harness CI pipeline that executes Vibgrate drift scanning. Learn how to gate the build and push results to Vibgrate Cloud.
Add a Vibgrate drift scan step to a Woodpecker CI pipeline using a Node container. Learn how to gate builds and generate a report.
Run Vibgrate drift scanning as a step in an Argo Workflows template on Kubernetes. Learn how to source the repository, gate the run, and capture the report.
Define a Tekton Task that runs Vibgrate drift scanning on a cloned workspace. Learn how to gate the pipeline run and emit the report.
Use --drift-budget to fail a pull request build when the DriftScore exceeds an allowed ceiling. Learn how to choose a budget and tighten it over time.
Produce a SARIF file with --format sarif and upload it to your platform's code scanning dashboard. Learn the scan command and how findings appear inline.
Turn a Vibgrate drift scan into a required status check so pull requests cannot merge while drift exceeds your gate. Learn the scan setup and the branch-protection side.
Run a full Vibgrate drift scan on a nightly schedule to track trend without slowing pull requests. Learn the scan command and how to push results for trend analysis.
Generate a Markdown drift report in CI and post it as a pull request comment so reviewers see the DriftScore inline. Learn the scan command and the posting pattern.
Use --changed-only to scan just the files touched in a pull request, keeping PR pipelines fast while reserving full scans for scheduled runs.
Persist the Vibgrate cache between CI runs to speed up repeat scans. Learn what to cache, how to key it, and when to bypass the cache.
Run parallel Vibgrate scans across a monorepo by fanning out a CI matrix over packages. Learn how to scope each scan and aggregate the DriftScores.
Use --push to upload CI scan results to Vibgrate Cloud for team visibility and trend analysis. Learn how to configure a DSN secret and run the push safely.
Use --fail-on to fail a build when findings reach a chosen severity. Learn how the flag maps to exit codes and how it complements a drift budget.
Set up Vibgrate in GitHub Actions for continuous drift detection, SARIF integration with Code Scanning, and automated dashboard uploads.
Set up Vibgrate in Azure DevOps Pipelines for continuous drift detection, SARIF artifact publishing, and drift budget enforcement.
Set up Vibgrate in GitLab CI/CD for continuous drift detection, SAST report integration, and drift budget enforcement.
Use Vibgrate in any CI system — Jenkins, CircleCI, Bitbucket Pipelines, or custom build scripts. The CLI requires no login, produces standard outputs, and works entirely offline.