Overview
Send Bitrise build results to Callgoose SQIBS. An outgoing webhook posts each finished build to your SQIBS API endpoint. SQIBS opens an incident when a build fails and resolves it when the next build of the same app succeeds.
How it works
build_status 2 (failed) opens it, 1 (success) 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.
- In Select Integration Template, choose Bitrise. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "build_status" |
2 |
Opens an incident. |
| Resolve | "build_status" |
1 |
Resolves the open incident. |
| Match | "app_slug" |
Ties the resolve message to the incident it opened. | |
| Title from | "build_triggered_workflow" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
Bitrise sends build_status as a number: 1 success, 2 failed, 3 aborted. The template matches on the app (app_slug), so one incident stays open per app until a build passes.
The template is a starting point, not a lock-in: every value stays visible and you can change it.
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 an outgoing webhook in Bitrise
- Open the project in Bitrise and click Project settings.
- On the left, select Integrations, then the Webhooks tab, and scroll down to Outgoing Webhooks. Click Add webhook.
- In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=bitrise&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.
- Choose Select individual events and tick the build events (or Send me everything).
- Add the header
Content-Type: application/jsonand save the webhook.
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.
- Start a build that fails, for example by adding a failing script step to a test workflow.
- In SQIBS, a new incident opens, titled with the workflow name. Bitrise's payload looks like this (shortened):
{
"build_slug": "fca38a91-32ba-429f-94c5-213ba4519f99",
"build_number": 42,
"app_slug": "c370e7ce-1925-4fb4-bf0d-fe331f309088",
"build_status": 2,
"build_triggered_workflow": "primary",
"git": {
"provider": "github",
"src_branch": "main",
"dst_branch": "main",
"pull_request_id": 0
}
}
- Fix the build and run it again. When Bitrise sends
"build_status": 1for the same app, 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 Bitrise webhook.
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 because a signing certificate expired, SQIBS can run a workflow that checks the certificate dates and posts the result to the incident before anyone looks.
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.