This guide adds Vibgrate drift scanning to Woodpecker CI, the open-source, container-native CI engine. It targets teams self-hosting Woodpecker alongside their git forge.
Prerequisites
- A Woodpecker pipeline file in your repository.
- A runner that can pull a Node container image.
Pipeline step
steps:
drift-scan:
image: node:22
commands:
- npx @vibgrate/cli scan --fail-on error
Woodpecker clones your repository into the workspace before steps run, so npx @vibgrate/cli scan scans the project root.
Quality gate
A non-zero exit code fails the step and the pipeline. Use --fail-on error to gate on error-severity findings, or --drift-budget to gate on the overall DriftScore:
npx @vibgrate/cli scan --drift-budget 60
Report output
Write a report into the workspace for a follow-up publish step:
npx @vibgrate/cli scan --format markdown --out drift-report.md
Caching
Use a cache plugin or mounted volume to persist the Vibgrate cache directory between builds. See Cache Vibgrate scans in CI for the general approach.
Related
- Scheduled nightly Vibgrate scans using Woodpecker cron.
- Push scan results to Vibgrate Cloud from CI for trends.