Buildkite support

Last updated date:

Connect, reconnect, and troubleshoot Buildkite without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the exact Buildkite organization and decide whether a dedicated service account should own lifecycle access.
  • Create a user API access token with read_user, read_organizations, read_pipelines, read_builds, read_artifacts, and read_teams only.
  • Record the organization slug when the token can see more than one organization.
  • Do not send Buildkite credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Buildkite API tokensBuildkite's API access-token guidance.

2. Connect Buildkite

  1. In Seedling, open Connections and choose Buildkite.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the API access token and optional organization slug; Seedling always calls the Buildkite API.
  4. Seedling verifies the token owner and target organization before creating the connection and rejects an inaccessible organization rather than falling back silently.
  5. Allow the first Buildkite synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Buildkite API access token rejected
Confirm the buildkite api access token is active, was entered without surrounding whitespace, and belongs to the intended Buildkite account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Buildkite population as empty.
Wrong account or scope
Disconnect before retrying with the intended Buildkite identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the pipeline and build belong to the selected organization and remain visible to the token owner.
  2. Check the read_pipelines, read_builds, read_artifacts, and read_teams scopes for the missing resource family.
  3. Confirm artifact retention or pipeline deletion in Buildkite has not removed the provider record.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement buildkite api access token for the same Buildkite account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old buildkite api access token in Buildkite.