bk job adds reprioritize and priority commands
Introduced 2026-02-11 · score 0.96
HOW TO USE IT
When the target job is in a running Buildkite build, set its new priority with `bk job reprioritize` and the job UUID and integer priority. The `bk job priority` alias is stated in the v3.24.0 release note; the official CLI reference documents `reprioritize`.
bk job reprioritize <job-uuid> <priority>WHY THIS HELPS
Change the priority of a job in a running Buildkite build.
REQUIREMENTS AND LIMITATIONS
- Version: v3.24.0
- <job-id> (required): UUID of the job to reprioritize.
- <priority> (required): New priority value for the job. API docs specify an integer; higher values indicate higher priority.
- -p, --pipeline: Pipeline slug or `org/pipeline`; current CLI reference marks this flag deprecated and ignored.
- -b, --build-number: Build number; current CLI reference marks this flag deprecated and ignored.
- Prerequisite: Configure the Buildkite CLI with an API access token.
- Prerequisite: The REST API reprioritize operation requires the `write_builds` scope.
- The job must be in a running build.
- Docs conflict: The v3.24.0 source example shows `-b <build>` and says `--pipeline` and `--build` are required unless the pipeline is configured for the current Git repository; the current CLI reference says both flags are deprecated and ignored. Follow the v3.24.0 source for that version-specific invocation if needed: https://github.com/buildkite/cli/blob/v3.24.0/cmd/job/reprioritize.go
- Docs conflict: The v3.24.0 release note names `job priority` as an alias, but the official CLI reference documents only `bk job reprioritize`; alias syntax was not found.
FIRST-PARTY EVIDENCE
- https://github.com/buildkite/cli/releases/tag/v3.24.0
- https://github.com/buildkite/cli/pull/641
- https://buildkite.com/docs/platform/cli/reference/job
- https://buildkite.com/docs/apis/rest-api/jobs
- https://buildkite.com/docs/platform/cli/configuration
Check the installed version and the source before using it. Entry JSON