Setting up delivery tracking

AccelerUp does not need to run your deploys to record them. It needs to be told about them.

The webhook

The general method. Post at the start and the end of a deploy:

# start
curl -X POST https://monitoring.qrdev.org/api/v1/deployments/webhook \
  -H "Authorization: Bearer $ACCELERUP_DEPLOY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
        "service":     "checkout-api",
        "environment": "production",
        "version":     "4.18.2",
        "commit":      "'"$GIT_COMMIT"'",
        "repo":        "org/checkout-api",
        "status":      "running",
        "triggered_by":"'"$BUILD_USER"'"
      }'

# finish
curl -X POST https://monitoring.qrdev.org/api/v1/deployments/webhook \
  -H "Authorization: Bearer $ACCELERUP_DEPLOY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"service":"checkout-api","environment":"production",
       "version":"4.18.2","status":"succeeded"}'

Jenkins

If you use Jenkins, the integration records builds automatically — no webhook needed. Corrected Jenkinsfile examples live in docs/jenkins/ in the repository.

Add /api/v1/jenkins/notify as a Jenkins notification endpoint for real-time status rather than waiting for the poll.

Smoke tests

A smoke test is an HTTP check run against the freshly deployed version, in the pipeline after deploy and before promote.

Settings → Deployments → Smoke tests. Keep them fast and narrow: a request that proves the thing starts and serves, not a test suite.

The token

Settings → Deployments → Setup issues the deploy token. It is scoped to deployment endpoints only — a token in CI should not be able to read your alert history.

Verifying

Deploy something to a non-production environment and check Delivery → Deployments → History. You should see the version, the changeset and, after the health window, a score.

If the changeset is empty, the commit was not sent or the repository could not be resolved — the deployment page says which.