> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/buildkite.md).

# Buildkite

Steps to configure Buildkite integration for incident management, using Squadcast.

[<mark style="color:blue;">Buildkite</mark>](https://buildkite.com/) is a platform for running fast, secure, and scalable continuous-integration pipelines on your own infrastructure.

Route detailed alerts from Buildkite to the right users in Squadcast.

### Using Buildkite as an Alert Source

1. Navigate to **Services** -> **Service Overview** -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click **Add**.

![](https://1574591692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8TaWz01jmUJl58p4ZVel%2Fuploads%2Fgit-blob-4fbd74e7ca0b30173c47a1d58ed6a0804a0465aa%2FAlert_Sources.png?alt=media\&token=aaca6610-9d18-4dd4-9cf5-320042f326f1)

2\. Select **Buildkite**. Copy the displayed **Webhook URL** to [configure](#create-a-squadcast-webhook-in-buildkite) it within **Buildkite**. Finish by clicking **Add Alert Source** -> **Done**.

![](https://1574591692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8TaWz01jmUJl58p4ZVel%2Fuploads%2Fgit-blob-8a97599a04d38512274dc380b8816f78b68d4d94%2FBuildkite.png?alt=media\&token=473fad03-ecea-4ee6-ba23-f93230e4991e)

{% hint style="warning" %} <mark style="color:orange;">**Important**</mark>**:**

When an alert source turns <mark style="color:green;">Active</mark>, it’ll show up under Configured Alert Sources. You can either generate a test alert from the integration or wait for a real-time alert to be generated by the Alert Source.\
\
An Alert Source is <mark style="color:green;">active</mark> if there is a recorded incident via that Alert Source for the Service.
{% endhint %}

### Create a Squadcast webhook in Buildkite

1. Login to your build kite web console and go to **Settings** tab on the top.

![](https://1574591692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8TaWz01jmUJl58p4ZVel%2Fuploads%2Fgit-blob-94530e73d9ac93cca4173d811d4b4fd477f15aad%2Fbuildkite_2.png?alt=media\&token=df77aa76-f268-485d-b56c-0a180c6449e8)

2.Click on **Notification Services** on left sidebar.

![](https://1574591692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8TaWz01jmUJl58p4ZVel%2Fuploads%2Fgit-blob-3a7283af805bf285b13c91a698fd3cb03196fb6d%2Fbuildkite_3.png?alt=media\&token=43a2ce1a-fb1e-48e0-93cd-5413324885bd)

3.Click on **Add** button beside Webhook.

![](https://1574591692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8TaWz01jmUJl58p4ZVel%2Fuploads%2Fgit-blob-33d51ea7ff28bb1e5e4347e09bc35be2714a414b%2Fbuildkite_4.png?alt=media\&token=6c86ae0a-2af0-46c0-9460-6d19fe534623)

4.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
```

![](https://1574591692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8TaWz01jmUJl58p4ZVel%2Fuploads%2Fgit-blob-7fbd10bc282f8c318a408a1af13b0328cd8b6457%2Fbuildkite_5.png?alt=media\&token=22f25138-6373-46b6-863f-66dc2032b276)

5.Configure the **Pipelines** and **Branch filtering** sections as per your requirements. 6.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.

*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*