CI/CD release gates

CI/CD release gates

Make quality a build step. Trigger a Workbook (functional and/or AI-quality) on every deploy and fail the pipeline if a journey regresses or a model's quality drops below threshold.

Pattern

1. Build a Workbook that proves the critical journey (and/or runs an AI Eval Suite).
2. From your pipeline, start it and wait for the result.
3. Fail the build on a failed/regressed status — catching problems before customers.

Pipeline snippet

# 1) start the run
EID=$(curl -fsS -X POST https://app.verops.io/api/workflow-executions/run \
  -H "Authorization: Bearer $VEROPS_TOKEN" -H "Content-Type: application/json" \
  -d '{"workflowId": 51, "triggeredBy": "ci"}' | jq -r .executionId)

# 2) poll until terminal
while :; do
  ST=$(curl -fsS https://app.verops.io/api/workflow-executions/$EID \
        -H "Authorization: Bearer $VEROPS_TOKEN" | jq -r .status)
  [ "$ST" = "completed" ] && exit 0
  [ "$ST" = "failed" ]    && { echo "VerOps gate failed"; exit 1; }
  sleep 5
done

Scheduling vs gating

The same Workbook can gate in CI and run on a schedule as a continuous monitor — one artifact, two jobs.