Overview
Send Azure Pipelines build results to Callgoose SQIBS. An Azure DevOps service hook posts every completed build to your SQIBS API endpoint. SQIBS opens an incident when a build fails and resolves it when the next build of the same pipeline succeeds.
How it works
failed opens it, succeeded closes it.Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.
Step 1: Add the API filter in SQIBS
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- Add a filter with these values (there is no built-in Azure DevOps template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "resource"."result" |
failed |
Opens an incident. |
| Resolve | "resource"."result" |
succeeded |
Resolves the open incident. |
| Match | "resource"."definition"."name" |
The pipeline name ties the next good build to the failure. | |
| Title from | "message"."text" |
Becomes the incident title. | |
| Description from | "detailedMessage"."text" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
For YAML pipelines you can use the Run state changed event instead; its result is under "resource"."run"."result" and the pipeline name under "resource"."pipeline"."name".
Not sure of a key? Send one test message first (step below), then build the filter from the real payload.
In the API Integration window, click the round
{} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.Step 2: Add a service hook in Azure DevOps
- In the project, open Project settings > Service hooks and click Create subscription.
- Choose Web Hooks and click Next.
- Set the trigger to Build completed. Pick the pipeline under Build pipeline (or leave it on any), and keep Build status on [Any] so successes reach SQIBS too.
- In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=azurepipelines&token=<your-token>
Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.
- Click Test to send a sample event, then Finish.
Step 3: Test it
The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.
- Click Test in the subscription, or run a build that fails.
- In SQIBS, a new incident opens, titled with the build message. The event looks like this (shortened):
{
"eventType": "build.complete",
"message": {
"text": "Build 20261122.3 failed"
},
"detailedMessage": {
"text": "Build 20261122.3 failed. Reason: individual CI by A. Developer"
},
"resource": {
"result": "failed",
"status": "completed",
"buildNumber": "20261122.3",
"definition": {
"id": 12,
"name": "shop-api-ci"
},
"url": "https://dev.azure.com/example/shop/_build/results?buildId=4812"
}
}
- When a later build of the same pipeline succeeds, SQIBS resolves the incident.
No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the service hook.
Fix known issues automatically
Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when a release build fails on a flaky agent, SQIBS can run a workflow that clears the agent's work folder and queues the build again.
Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.
To set it up, in the same API filter:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.
Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.
Learn more:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.