From Buildkite

Mapping a self-run Buildkite pipeline onto codev — coming soon.

The approach to moving a Buildkite pipeline onto codev is the same as any other CI: connect the repository to sfp server, then hand build-on-merge, releases, pools, and validation to the server one at a time. Read Migrating to codev for that end-to-end flow.

A Buildkite-specific walkthrough — mapping your pipeline steps and agent configuration onto codev, the way From GitHub Actions maps a GitHub Actions workflow — is in progress.

In the meantime, the CI-agnostic parts apply directly:

• Connect the repository. Onboarding registers the webhooks the server listens on, so a merge notifies codev without a Buildkite trigger. See Step 1 and the source control integration for your host.
• Hand over build-on-merge. Turn it on per domain from Workflow Settings; the server builds on its own image, so there is no sfp image to pin in your Buildkite agents. See Step 2.
• Keep the rest of your pipeline running until you move each part — provided those steps run sfp-pro on the same release as the server (see While you still run some builds yourself).

The handover control is the same whatever CI you come from: turn on server builds per branch and per domain from Workflow Settings, while your Buildkite pipeline keeps running everything else.