Pipelines and CI/CD integration

Pipelines and CI/CD integration

Workbooks → Pipelines (/workbooks/pipelines) and Settings → Pipeline integration connect workbooks to your delivery pipeline so a run gates a deploy.

Cookbook: gate a deploy

1. Build (or pick) the workbook that proves your critical journey and/or runs an AI eval suite.
2. In Pipeline integration, get the trigger details (workbook id, token).
3. From your pipeline, start the run and fail the build if it fails:

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)
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

Git-backed workbooks

Settings → Git repo lets you connect a repository so workbook definitions are version-controlled alongside your code — review changes in PRs and keep environments in sync.