Skip to main content
Book a demo

Connect Buildkite to Oh My Pi

Give Oh My Pi governed access to Buildkite’s 71 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Oh My Pi setup guide

Set up

Add Buildkite to Oh My Pi in four steps

Admins approve the server once. Everyone in Oh My Pi then gets it through the same governed connection.

  1. 1

    Approve Buildkite in Runlayer

    Add Buildkite from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Oh My Pi to Runlayer

    Users add the Runlayer Plugin to Oh My Pi by following Runlayer’s setup guide. Oh My Pi reaches Buildkite’s 71 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Oh My Pi setup guide
  3. 3

    Sign in to Buildkite

    Sign in the way Buildkite requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Buildkite from Oh My Pi

    Buildkite’s approved tools appear in Oh My Pi. Every call is checked against policy and recorded.

Tools

71 Buildkite tools in Oh My Pi

Runlayer policy decides which of these Oh My Pi users can call.

  • Access token

    Get information about the current API access token including its scopes and UUID

  • Cancel build

    Cancel a running build on a Buildkite pipeline

  • Compare builds

    Compare step outcomes, final-attempt retry counts and execution/scheduling times between builds in one pipeline.

  • Create annotation

    Create an annotation on a build or specific job.

  • Create build

    Trigger a new build on a Buildkite pipeline for a specific commit and branch, with optional environment variables, metadata, and author information

  • Create cache registry

    Create a cache registry in a cluster.

  • Create cluster

    Create a new cluster in an organization

  • Create cluster queue

    Create a new queue in a cluster

See all 71 Buildkite tools

Control

What Runlayer can see and stop in Oh My Pi

Some controls apply to every client at the gateway. Others depend on what Oh My Pi exposes to Runlayer.

  • Gateway policy (available)

    Every Buildkite call from Oh My Pi passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Oh My Pi as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Oh My Pi yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination