Setup Buildkite Integration
Last updated
Last updated
To integrate Buildkite with your CI-Engine subscription, follow the steps below:
Navigate to CI-Engine > .
Click on the (+) Plus sign.
Choose the subscription for which you create the integration.
Choose Buildkite as the CI-provider of the integration.
Choose a global or custom image for your runners to use.
You can always later.
Configure the runners to connect to your repository.
Setup an
Define a runner timeout, after which a runner without an active build job will be terminated.
Give your integration a name.
Configure a
Add the displayed public .
Once you finished the steps above you are ready to build! Simply trigger the Workflow you just updated to run on CI-Engine and check the state of your runners on the detail page of your subscription.
The is used to authenticate and connect the agent on each new runner to your pipeline. We support both clustered and unclustered tokens. However we strongly suggest the usage of a clustered agent token as this is the new default for Buildkite agent tokens. You can find out more about unclustered Buildkite agent tokens .
To spawn the runners on demand you need to setup Webhooks in your Buildkite pipeline:
In your Buildkite dashboard, go to Settings > Notification Services and click on the Add-Button for webhooks.
Configure the Webhook URL and the Token that are provided in the Wizard-Step. Alternatively you can find this information on the details page of your integration by clicking on (•••) More button and View Webhook Config.
Configure the Webhook Notifications by selecting the Events job.scheduled and job.finished. These Events are required for the runners to spawn correctly.
To give the runner access to clone your repository during the jobs you need to add the SSH public key that is provided on this step to your git provider. Most providers support a deploy key that can be used for this purpose. For more instructions you can follow the official documentation of your provider: