Easily Integrate Buildkite Webhooks with your application.
https://buildkite.com/docs/apis/webhooks
Steps to receive Buildkite Webhooks
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select Buildkite. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
- Step 1
- Step 2
- Once a webhook is received from Buildkite, you'll see it under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.
Integrating Buildkite Webhooks Using Javascript
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select Buildkite. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
- Step 1
- Step 2
- Once a webhook is received from Buildkite, you'll see it under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.
Integrating Buildkite webhooks with Hooky in your Javascript based application is straight forward. Just grab the SDK, and call a function when that webhook is received.
Integrating Buildkite Webhooks Using Ruby
Integrating Buildkite webhooks with Hooky in your Ruby or Ruby on Rails application is straight forward. Just grab the SDK, and call a method when that webhook is received.
Configuring Buildkite Webhook Authentication
Here's how it works
Supported Buildkite Webhook Events
ping
Webhook notification settings have changed
build.scheduled
A build has been scheduled
build.running
A build has started running
build.finished
A build has finished
job.scheduled
A job has been scheduled
job.started
A command step job has started running on an agent
job.finished
A job has finished
job.activated
A block step job has been unblocked using the web or API
agent.connected
An agent has connected to the API
agent.lost
An agent has been marked as lost. This happens when Buildkite stops receiving pings from the agent
agent.disconnected
An agent has disconnected. This happens when the agent shuts down and disconnects from the API
agent.stopping
An agent is stopping. This happens when an agent is instructed to stop from the API. It first transitions to stopping and finishes any current jobs
agent.stopped
An agent has stopped. This happens when an agent is instructed to stop from the API. It can be graceful or forceful