bk commands accept a global --org flag

Introduced 2026-10-08 · score 0.98

HOW TO USE IT

When a `bk` command must use a different organization for one invocation, add `--org <organization-slug>` to the command or place it before the command. This selects that organization’s stored credentials and overrides environment and saved defaults; qualified targets must agree with it.

WHY THIS HELPS

Run a `bk` command against a different Buildkite organization while preserving saved organization and pipeline defaults.

BEFORE THIS CHANGE

Build list and view relied on the selected organization; multi-organization use required changing the selected organization or configuration.

REQUIREMENTS AND LIMITATIONS

• Version: v3.61.1
• --org <organization-slug>: Selects an organization for this invocation, overrides `BUILDKITE_ORGANIZATION_SLUG` and repository/user defaults, and selects that organization's stored credentials. Qualified pipeline or build targets must agree with it.
• --pipeline <pipeline-slug>: Specifies the pipeline; provide it when the effective organization differs from the saved organization and a cached pipeline name would otherwise be used.
• --target org/name: For `pipeline copy`, specifies a destination organization and pipeline independently of `--org`, which selects the source organization.
• Prerequisite: Install the Buildkite CLI and authenticate/configure credentials for the target organization so its stored credentials are available.
• Prerequisite: An explicit `BUILDKITE_API_TOKEN` takes precedence over stored credentials.
• Explicit API environment tokens retain precedence.
• Qualified pipeline or build targets, including URLs, must agree with an explicit `--org`; disagreements error before execution.
• When the effective organization differs from the saved selection, cached pipeline names are ignored; provide `--pipeline` or allow repository discovery to find a pipeline in the target organization.
• Repository pipeline discoveries made with `--org` or `BUILDKITE_ORGANIZATION_SLUG` are not cached.
• For `pipeline copy`, `--org` selects the source organization; `--target org/name` can select a different destination.
• Authentication and configuration commands retain their existing credential or selection changes.

FIRST-PARTY EVIDENCE

• https://github.com/buildkite/cli/releases/tag/v3.61.1
• https://github.com/buildkite/cli/pull/1024
• https://github.com/buildkite/cli/blob/v3.61.1/README.md

Check the installed version and the source before using it. Entry JSON

Report a problem with this card