Buildkite Cli

作者 buildkite50c85f20d409无许可证18 个星标收录于 2026年10月8日更新于 2026年10月8日仓库2周前更新

This skill should be used when the user asks to "trigger a build", "check build status", "watch a build", "view build logs", "rebuild a build", "cancel a build", "list builds", "list jobs", "unblock a job", "download artifacts", "manage secrets", "create a pipeline", "list pipelines", "validate a pipeline", "copy a pipeline", "run a local agent", or "interact with Buildkite from the command line". Also use when the user mentions bk commands, bk build, bk job, bk pipeline, bk secret, bk artifacts, bk cluster, bk queue, bk package, bk agent, bk auth, bk config, bk use, bk browse, bk api, bk skill, or asks about Buildkite CLI installation, authentication, terminal-based Buildkite workflows, or command-line CI/CD operations.

仅含说明DevOps & Cloud

AI 生成的概览

指导使用 Buildkite CLI（bk）管理构建、任务、流水线、密钥、制品、集群与代理。

功能: 该技能提供在终端中使用 bk 命令行工具操作 Buildkite 的说明与命令示例。内容涵盖触发、查看、列出、监视、取消和重建构建；查看任务日志以及重试或解除阻塞任务；创建、复制和校验流水线；管理集群范围的密钥；列出和下载制品；管理集群、队列和本地代理；以及发起原始 REST 或 GraphQL 调用。它还将 CLI 命令与 Buildkite MCP 工具对应起来，并列出常见错误。
适用场景: 当用户想要触发或监控 Buildkite 构建、查看或操作任务、管理流水线、密钥、制品、集群或队列，或以其他方式从命令行使用 Buildkite 时使用。也适用于关于 bk 安装、身份验证和基于终端的 CI/CD 工作流的问题。
运行要求: 需要安装 Buildkite CLI（bk），通常通过 Homebrew 安装，并通过 OAuth 登录或具有相应权限范围的 API 令牌进行身份验证。需要访问 Buildkite 的网络；部分命令需要 git 仓库以自动识别流水线。不包含脚本，只有说明文档和一份参考文档。

Buildkite CLI

The Buildkite CLI (bk) provides terminal access to builds, jobs, pipelines, secrets, artifacts, clusters, queues, and packages. Use it to trigger builds, tail logs, manage secrets, run a local agent, and automate CI/CD workflows without leaving the command line.

Tip: This skill covers common commands and patterns. For complete flag details on any command, run bk <command> --help. The CLI ships exhaustive examples in its own help output — prefer it as the source of truth for a specific flag.

Quick Start

bk job list --build requires Buildkite CLI v3.53.0 or later. Run bk update if the flag is unavailable.

bash

# Installbrew install buildkite/buildkite/bk
# Authenticate (OAuth — opens a browser)bk auth login
# Trigger a build on the current branch (pipeline auto-detected from the repo)bk build create
# Watch the most recent build runbk build watch
# Inspect build state, find failed jobs, and read a failed job's logbk build view 429 --summarybk job list --pipeline my-app --build 429 --state failedbk job log <job-uuid>

# Installbrew install buildkite/buildkite/bk
# Authenticate (OAuth — opens a browser)bk auth login
# Trigger a build on the current branch (pipeline auto-detected from the repo)bk build create
# Watch the most recent build runbk build watch
# Inspect build state, find failed jobs, and read a failed job's logbk build view 429 --summarybk job list --pipeline my-app --build 429 --state failedbk job log <job-uuid>

Most build, job, artifact, and pipeline commands resolve the pipeline, branch, and most-recent build from the current git repository. Pass -p/--pipeline explicitly only when outside a repo or when targeting a different pipeline.

Installation

bash

# Homebrew (macOS and Linux)brew install buildkite/buildkite/bk
# Update an existing install (prints the right command for brew/mise installs)bk update

# Homebrew (macOS and Linux)brew install buildkite/buildkite/bk
# Update an existing install (prints the right command for brew/mise installs)bk update

For binary downloads and verification, see references/command-reference.md.

Authentication

bk auth login is the recommended method. It uses OAuth and stores the resulting token in the system keychain — no manual token creation required.

bash

# OAuth login (opens a browser; grants all scopes your account allows)bk auth login
# Login to a specific organizationbk auth login --org my-org
# Login with read-only access (scope group), plus write access to buildsbk auth login --scopes "read_only write_builds"
# Headless / remote machine (no browser)bk auth login --device
# Non-interactive with an existing API token (CI/Docker)bk auth login --org my-org --token "$BUILDKITE_API_TOKEN"

# OAuth login (opens a browser; grants all scopes your account allows)bk auth login
# Login to a specific organizationbk auth login --org my-org
# Login with read-only access (scope group), plus write access to buildsbk auth login --scopes "read_only write_builds"
# Headless / remote machine (no browser)bk auth login --device
# Non-interactive with an existing API token (CI/Docker)bk auth login --org my-org --token "$BUILDKITE_API_TOKEN"

Command	Description
`bk auth login`	OAuth or token login; stores credentials in the keychain
`bk auth status`	Show the current session (supports `-o json`)
`bk auth token`	Print the stored token to stdout (e.g. for `curl`)
`bk auth switch [org]` (alias `bk auth use`)	Switch the active organization
`bk auth logout`	Remove stored credentials (`--all` for every org)

On headless Linux hosts where no keychain is available, pin token storage to an in-memory store: bk config set credential_store shm, then bk auth login --device.

Token-based config (alternative)

bk configure stores a manually-created API token instead of using OAuth. Use it only when OAuth is unavailable.

bash

bk configure --org my-org --token "$BUILDKITE_API_TOKEN"bk configure add --org second-org --token "$OTHER_TOKEN"   # add another org

bk configure --org my-org --token "$BUILDKITE_API_TOKEN"bk configure add --org second-org --token "$OTHER_TOKEN"   # add another org

Create the token at Buildkite > avatar > Personal Settings > API Access Tokens with at least read_builds, write_builds, read_pipelines, and read_artifacts scopes.

Switching organizations

bash

bk use my-other-org      # top-level alias for bk auth switchbk auth switch           # interactive selectionbk organization list     # list configured orgs

bk use my-other-org      # top-level alias for bk auth switchbk auth switch           # interactive selectionbk organization list     # list configured orgs

CLI configuration

bk config manages persistent settings (default output format, pager, credential store). User config applies globally; --local writes a .bk.yaml in the current directory.

bash

bk config list                          # show effective configbk config set output_format json        # default all output to JSONbk config set selected_org my-org --local

bk config list                          # show effective configbk config set output_format json        # default all output to JSONbk config set selected_org my-org --local

Builds

Create, view, list, cancel, retry, rebuild, watch, and download builds.

Create a build

bash

# Build the current branch and commit (pipeline auto-detected from the repo)bk build create
# Explicit pipeline, branch, and messagebk build create -p my-app -b feature/auth -m "Test auth changes"
# With environment variables and metadatabk build create -e "DEPLOY_ENV=staging" -M "release=true"
# Open the new build in the browserbk build create -w

# Build the current branch and commit (pipeline auto-detected from the repo)bk build create
# Explicit pipeline, branch, and messagebk build create -p my-app -b feature/auth -m "Test auth changes"
# With environment variables and metadatabk build create -e "DEPLOY_ENV=staging" -M "release=true"
# Open the new build in the browserbk build create -w

Flag	Short	Default	Description
`--pipeline`	`-p`	auto-detected	Pipeline slug, or `{org}/{slug}`
`--branch`	`-b`	pipeline default branch	Git branch to build
`--commit`	`-c`	`HEAD`	Git commit SHA
`--message`	`-m`	commit message	Build message
`--author`	`-a`	—	Build author (`"Name <email>"`, email, name, or username)
`--env`	`-e`	—	Environment variable `KEY=VALUE` (repeatable)
`--env-file`	`-f`	—	Load environment variables from a file
`--metadata`	`-M`	—	Build metadata `KEY=VALUE` (repeatable)
`--ignore-branch-filters`	`-i`	`false`	Build even when branch filters would skip it
`--web`	`-w`	`false`	Open the build in a browser after creating it

View a build

bk build view (and most build commands) default to the most recent build on the current branch.

Use --summary for status checks, polling, scripts, and agent workflows. It excludes jobs and expanded pipeline information, and skips artifact and annotation requests.

bash

bk build view --summary             # latest build metadata and statebk build view 429 --summary         # a specific build numberbk build view 429 --summary -o json # compact structured outputbk build view --mine --summary      # latest build by the current user

bk build view --summary             # latest build metadata and statebk build view 429 --summary         # a specific build numberbk build view 429 --summary -o json # compact structured outputbk build view --mine --summary      # latest build by the current user

List builds

bash

bk build list --summary                              # 50 most recent build summariesbk build list --summary --state failed --branch main # filter by state and branchbk build list --summary --since 24h --duration ">20m" # slow builds from the last 24 hoursbk build list --summary --meta-data env=production -o json

bk build list --summary                              # 50 most recent build summariesbk build list --summary --state failed --branch main # filter by state and branchbk build list --summary --since 24h --duration ">20m" # slow builds from the last 24 hoursbk build list --summary --meta-data env=production -o json

Use --summary for metadata-only output; the API requests exclude jobs and expanded pipeline information. Server-side filters (fast): --pipeline, --since, --until, --state, --branch, --creator, --commit, --meta-data. Client-side filters: --duration, --message. Valid states: running, scheduled, passed, failed, blocked, canceled, canceling, skipped, not_run. Pass --state and --branch as comma-separated lists. Use --limit N (default 50) or --no-limit to control paging. See references/command-reference.md for the full filter table.

Watch a build

Stream real-time progress. Blocks until the build completes or is canceled.

bash

bk build watch                       # watch the most recent buildbk build watch 429 -p my-app         # watch a specific buildbk build watch --interval 5          # custom polling interval (seconds)

bk build watch                       # watch the most recent buildbk build watch 429 -p my-app         # watch a specific buildbk build watch --interval 5          # custom polling interval (seconds)

Cancel, retry, rebuild

bash

bk build cancel 429 -p my-app   # only scheduled/running/failing buildsbk build rebuild 429            # rebuild a specific build (or most recent)

bk build cancel 429 -p my-app   # only scheduled/running/failing buildsbk build rebuild 429            # rebuild a specific build (or most recent)

Download build resources

bk build download downloads a build's artifacts to the local filesystem.

bash

bk build download 429 -p my-appbk build download --mine          # most recent build by the current user

bk build download 429 -p my-appbk build download --mine          # most recent build by the current user

Trigger and follow

Jobs

Inspect and act on individual jobs. Jobs are addressed by UUID — bk job log no longer needs pipeline or build context (the -p/-b flags are deprecated and ignored).

View job logs

bash

bk job log 0190046e-e199-453b-a302-a21a4d649d31bk job log <job-uuid> --no-timestamps   # strip timestamp prefixes

bk job log 0190046e-e199-453b-a302-a21a4d649d31bk job log <job-uuid> --no-timestamps   # strip timestamp prefixes

List jobs

--step-key and --group-key require Buildkite CLI v3.54.0 or later. Run bk update if either flag is unavailable.

When the build number is known, pass --build so bk job list uses the dedicated cursor-paginated List Jobs endpoint. The pipeline can be explicit or resolved from the current repository or configuration. --state, --step-key, and --group-key are applied server-side; --queue and --duration remain client-side. Use --step-key for every job in a step, including parallel jobs, and --group-key for every job in a group.

bash

bk job list --pipeline my-app --build 429 --state failedbk job list --build 429 --state running # pipeline auto-detectedbk job list --build 429 --step-key testbk job list --build 429 --group-key verification

bk job list --pipeline my-app --build 429 --state failedbk job list --build 429 --state running # pipeline auto-detectedbk job list --build 429 --step-key testbk job list --build 429 --group-key verification

Without --build, the command searches across recent builds and extracts their embedded jobs:

bash

bk job list --queue test-queue --state runningbk job list --duration ">10m" --order-by duration --no-limit

bk job list --queue test-queue --state runningbk job list --duration ">10m" --order-by duration --no-limit

--step-key and --group-key require --build and can be combined. --limit caps the total jobs emitted, not the API page size. Use --no-limit to follow every cursor page; the CLI preserves all server-side filters across cursor pages. --since and --until cannot be combined with --build.

Retry, cancel, unblock, reprioritize

bash

bk job retry <job-uuid>           # each job UUID can be retried oncebk job cancel <job-uuid>bk job unblock <job-uuid>         # unblock a blocked stepbk job unblock <job-uuid> --data '{"release": "true"}'   # with block-step fieldsbk job reprioritize <job-uuid> 10 # raise scheduling priority

bk job retry <job-uuid>           # each job UUID can be retried oncebk job cancel <job-uuid>bk job unblock <job-uuid>         # unblock a blocked stepbk job unblock <job-uuid> --data '{"release": "true"}'   # with block-step fieldsbk job reprioritize <job-uuid> 10 # raise scheduling priority

Debugging workflow

bash

bk build list --summary --state failed -p my-appbk job list --pipeline my-app --build 429 --state failedbk job log <job-uuid>

bk build list --summary --state failed -p my-appbk job list --pipeline my-app --build 429 --state failedbk job log <job-uuid>

Pipelines

Create, list, view, copy, validate, and convert pipeline configuration.

List and view

bash

bk pipeline list                 # all pipelines (default 100)bk pipeline list --name deploy   # filter by name (partial, case-insensitive)bk pipeline view my-app          # pipeline detailsbk pipeline view my-app -w       # open in browser

bk pipeline list                 # all pipelines (default 100)bk pipeline list --name deploy   # filter by name (partial, case-insensitive)bk pipeline view my-app          # pipeline detailsbk pipeline view my-app -w       # open in browser

Create a pipeline

bash

bk pipeline create "My App" -r "[email protected]:org/my-app.git" --cluster-name "Default"bk pipeline create "My App" -r "[email protected]:org/my-app.git" --dry-run   # synthetic non-mutating preview

bk pipeline create "My App" -r "[email protected]:org/my-app.git" --cluster-name "Default"bk pipeline create "My App" -r "[email protected]:org/my-app.git" --dry-run   # synthetic non-mutating preview

Flag	Short	Default	Description
`<name>`	—	—	Pipeline name (positional, required)
`--repository`	`-r`	—	Git repository URL
`--description`	`-d`	—	Pipeline description
`--cluster-uuid`	—	—	Cluster UUID to assign the pipeline to
`--cluster-name`	—	—	Cluster name (resolved to UUID)
`--create-webhook`	`-W`	`false`	Create a GitHub or GitHub Enterprise SCM webhook after pipeline creation
`--dry-run`	—	`false`	Print a synthetic preview without creating the pipeline; may make read-only API calls

Treat pipeline creation and --create-webhook as non-atomic operations: pipeline creation can succeed while SCM webhook creation fails. An SCM webhook delivers repository events and is distinct from an outbound organization notification-service webhook.

For pipeline YAML configuration, step types, and plugins, see the buildkite-pipelines skill.

Copy a pipeline

bash

bk pipeline copy my-app --target "my-app-v2"             # within the orgbk pipeline copy my-app --target "other-org/my-app"      # across orgs (cluster reset)

bk pipeline copy my-app --target "my-app-v2"             # within the orgbk pipeline copy my-app --target "other-org/my-app"      # across orgs (cluster reset)

Validate a pipeline

bk pipeline validate checks YAML against the pipeline schema locally (no API token needed). It does not check repository access, source-control provider setup, permissions, or server-side pipeline creation constraints. Defaults to .buildkite/pipeline.yaml or .yml.

Convert from another CI system

Convert GitHub Actions, Bitbucket, CircleCI, Jenkins, GitLab (beta), Harness (beta), or Bitrise (beta) config to Buildkite YAML. No login required.

bash

bk pipeline convert -F .github/workflows/ci.yml          # vendor auto-detectedbk pipeline convert -F .gitlab-ci.yml --vendor gitlab    # specify when ambiguouscat .circleci/config.yml | bk pipeline convert --vendor circleci

bk pipeline convert -F .github/workflows/ci.yml          # vendor auto-detectedbk pipeline convert -F .gitlab-ci.yml --vendor gitlab    # specify when ambiguouscat .circleci/config.yml | bk pipeline convert --vendor circleci

Output defaults to .buildkite/pipeline.<vendor>.yml (stdout when reading from stdin). Use -o/--output for a custom path.

For converting pipelines from other CI systems in depth, see the buildkite-migration skill.

Secrets

Manage cluster-scoped secrets. All secret commands require --cluster-uuid.

bash

# Create (omit --value to enter it via a masked prompt)bk secret create --cluster-uuid <uuid> --key MY_SECRET --value "$TOKEN"
# List, view, update, deletebk secret list --cluster-uuid <uuid>bk secret get --cluster-uuid <uuid> --secret-id <secret-uuid>bk secret update --cluster-uuid <uuid> --secret-id <secret-uuid> --update-valuebk secret delete --cluster-uuid <uuid> --secret-id <secret-uuid>

# Create (omit --value to enter it via a masked prompt)bk secret create --cluster-uuid <uuid> --key MY_SECRET --value "$TOKEN"
# List, view, update, deletebk secret list --cluster-uuid <uuid>bk secret get --cluster-uuid <uuid> --secret-id <secret-uuid>bk secret update --cluster-uuid <uuid> --secret-id <secret-uuid> --update-valuebk secret delete --cluster-uuid <uuid> --secret-id <secret-uuid>

Naming rules: keys may contain only letters, numbers, and underscores, and cannot begin with buildkite or bk (case-insensitive). Exception: BUILDKITE_API_TOKEN. Pass --description and an access --policy (YAML) on create or update.

For using secrets inside pipeline YAML (secrets:) and job steps (buildkite-agent secret get), see the buildkite-pipelines and buildkite-agent-runtime skills.

Artifacts

List and download build artifacts. The command is bk artifacts (plural). Build number defaults to the most recent build on the current branch.

bash

bk artifacts list                              # most recent buildbk artifacts list 429 -j <job-uuid>            # a specific job in a buildbk artifacts download --build 429              # all artifacts for a buildbk artifacts download <artifact-id> --build 429

bk artifacts list                              # most recent buildbk artifacts list 429 -j <job-uuid>            # a specific job in a buildbk artifacts download --build 429              # all artifacts for a buildbk artifacts download <artifact-id> --build 429

There is no bk artifacts upload. Upload artifacts from within a job step with buildkite-agent artifact upload (see the buildkite-agent-runtime skill). For artifact_paths: in pipeline YAML, see the buildkite-pipelines skill.

Clusters and Queues

The CLI manages clusters, queues, and cluster maintainers directly:

bash

bk cluster listbk cluster create --name "Production"bk queue list <cluster-uuid>bk queue create <cluster-uuid> --key deploybk queue pause <cluster-uuid> <queue-uuid>     # stop dispatching to a queue

bk cluster listbk cluster create --name "Production"bk queue list <cluster-uuid>bk queue create <cluster-uuid> --key deploybk queue pause <cluster-uuid> <queue-uuid>     # stop dispatching to a queue

Full CRUD exists for bk cluster, bk queue, and bk maintainer. See references/command-reference.md for the command list.

Local Agent

bk agent run downloads the agent, creates a temporary cluster token, and runs an ephemeral buildkite-agent locally — useful for testing pipeline changes against your own machine. Everything is cleaned up on Ctrl+C.

bash

bk agent run                      # latest agent on the Default clusterbk agent run --queue deploy       # listen on a specific queuebk agent install                  # install the binary + a starter config

bk agent run                      # latest agent on the Default clusterbk agent run --queue deploy       # listen on a specific queuebk agent install                  # install the binary + a starter config

bk agent list/view/pause/resume/stop manage registered agents in the org.

Preflight, Browse, and Other Commands

bash

bk browse                 # open the current pipeline (filtered to the branch)bk browse 429 -n          # print the build URL instead of opening itbk init                   # scaffold a starter pipeline.yamlbk package push <registry-slug> --file-path pkg.tar.gzbk user invite [email protected] [email protected]bk skill add buildkite-api   # install a Buildkite skill into the current agent

bk browse                 # open the current pipeline (filtered to the branch)bk browse 429 -n          # print the build URL instead of opening itbk init                   # scaffold a starter pipeline.yamlbk package push <registry-slug> --file-path pkg.tar.gzbk user invite [email protected] [email protected]bk skill add buildkite-api   # install a Buildkite skill into the current agent

For running a build against local uncommitted changes with bk preflight run, see the buildkite-preflight skill.

Raw API Access

Make direct REST or GraphQL calls with bk api:

bash

bk api '/pipelines/my-app/builds/429?exclude_jobs=true&exclude_pipeline=true'bk api -X POST /pipelines --data '{"name":"New","repository":"git@..."}'bk api --file query.graphql # GraphQL file with a named operation

bk api '/pipelines/my-app/builds/429?exclude_jobs=true&exclude_pipeline=true'bk api -X POST /pipelines --data '{"name":"New","repository":"git@..."}'bk api --file query.graphql # GraphQL file with a named operation

For comprehensive REST and GraphQL documentation (endpoints, mutations, pagination, webhooks), see the buildkite-api skill.

MCP Server Alternatives

When the Buildkite MCP server is available, prefer MCP tools for read operations — they handle auth, pagination, and parsing. Fall back to the CLI for actions MCP does not cover.

CLI Command	MCP Tool	Notes
`bk build create`	`create_build`	MCP handles auth automatically
`bk build view --summary` / `list --summary`	`get_build` / `list_builds`	Metadata only; jobs and expanded pipeline information are excluded
`bk job list --build`	`list_jobs`	List jobs without expanding the build response
—	`get_job`	MCP-only single-job metadata lookup
`bk job log`	`read_logs`, `tail_logs`	MCP supports streaming
`bk pipeline list` / `view` / `create`	`list_pipelines`, `get_pipeline`, `create_pipeline`
`bk artifacts list` / `download`	`list_artifacts_for_build`, `get_artifact`
`bk cluster list`	`list_clusters`
`bk auth status`	`current_user`, `access_token`
`bk build watch` / `download`	—	CLI only
`bk job retry` / `cancel` / `unblock`	—	CLI only
`bk secret *`, `bk package push`, `bk agent run`	—	CLI only
`bk api`	—	Use MCP tools for reads; CLI for custom calls

Common Mistakes

Mistake	What happens	Fix
Using full build responses for status polling	Downloads jobs, pipeline details, artifacts, and annotations repeatedly	Use `bk build view --summary` or `bk build list --summary`
Omitting `--build` when the build number is known	Scans recent build responses and extracts their embedded jobs	Use `bk job list --pipeline my-app --build 429`, or MCP `list_jobs`
Running `bk` commands before authenticating	Commands fail with authentication errors	Run `bk auth login` (or `bk configure` with a token) first
Running `bk auth login` in Docker/CI expecting a browser	Hangs — no browser or keychain available	Use `bk auth login --org my-org --token "$TOKEN"`, or `--device` for headless
Passing `-p`/`-b` to `bk job log`	Flags are deprecated and ignored — job UUIDs are self-contained	Pass only the job UUID
Retrying a job UUID that was already retried	API returns 422 — each UUID retries once	Use the new job UUID returned by the first retry
Creating secrets with keys starting with `buildkite`/`bk`	Creation fails — reserved prefix	Choose another name (exception: `BUILDKITE_API_TOKEN`)
Passing secret values literally in `--value`	Values persist in shell history and process list	Use env var references (`--value "$TOKEN"`) or the masked prompt
Running `bk build cancel` on a finished build	API errors — only scheduled/running/failing builds cancel	Check state with `bk build view --summary` first
Assuming `bk artifacts upload` exists	No such command	Upload from a job with `buildkite-agent artifact upload`
Confusing `bk` with `buildkite-agent`	`bk` runs locally against the API; `buildkite-agent` runs inside job steps	Use `bk` from a terminal, `buildkite-agent` inside pipeline commands

Additional Resources

Reference Files

references/command-reference.md — Installation methods, full bk build list/bk job list filter tables, cluster/queue/maintainer commands, bk agent, bk api, package push, and config details

来源与署名

来源：buildkite/skills位于skills/buildkite-cli提交50c85f2

许可证：无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

Buildkite Cli

Buildkite CLI

Quick Start

Installation

Authentication

Token-based config (alternative)

Switching organizations

CLI configuration

Builds

Create a build

View a build

List builds

Watch a build

Cancel, retry, rebuild

Download build resources

Trigger and follow

Jobs

View job logs

List jobs

Retry, cancel, unblock, reprioritize

Debugging workflow

Pipelines

List and view

Create a pipeline

Copy a pipeline

Validate a pipeline

Convert from another CI system

Secrets

Artifacts

Clusters and Queues

Local Agent

Preflight, Browse, and Other Commands

Raw API Access

MCP Server Alternatives

Common Mistakes

Additional Resources

Reference Files

Further Reading

来源与署名

更多来自 buildkite/skills 的技能

Buildkite Preflight

Buildkite Migration

Buildkite Cache

Buildkite Agent Runtime

更多DevOps & Cloud技能

M5 Onboard

Spanner Basics

Secops Cases

Managed Airflow Migrations

Managed Airflow Dag Troubleshooting

Iam Helper For Privileged Access Management