Get alerts from Buildkite into Squadcast

Follow the steps below to configure a service so as to extract its related alert data from Buildkite.

Squadcast will then process this information to create incidents for this service as per your preferences.

Create a Buildkite Service in Squadcast

On the Sidebar, click on Services.

You can either navigate to an existing service or make a new one by clicking on Add Service.

Check the service details like name, description, and the associated escalation policy for this service and make sure it is correctly entered.

From the integration types drop down, select the integration type as Buildkite.

Enter the service name and description as required.

Copy the Buildkite Webhook URL and click on Save button to create the service.

Create a Squadcast webhook in Buildkite

  1. Login to your build kite web console and go to Settings tab on the top.
  1. Click on Notification Services on left sidebar.
  1. Click on Add button beside Webhook.
  1. Paste the Build Kite Webhook URL copied from the Squadcast dashboard into the Webhook URL field. In events, select :

    • build.finished
    • agent.connected
    • agent.lost
    • agent.disconnected
    • agent.stopped
  1. Configure the Pipelines and Branch filtering sections as per your requirements.
  2. Finally, click on the Add Webhook Notification

Now whenever a build fails in Buildkite, an incident will be created automatically in Squadcast.
And once the build for the same pipeline passes, all the Squadcast incidents created would get resolved automatically.

Similarly, when the agent gets disconnected / lost / stopped, an incident is created in Squadcast automatically. And once that agent is connected again, the incident is automatically resolved.

NOTE : The incident gets resolved automatically only if the same agent connects back. If a different agent connects, the user need to manually resolve the incident in the Squadcast Dashboard.

Updated 5 months ago


Get alerts from Buildkite into Squadcast

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.