bk job retry supports structured output
Introduced 2026-09-21 · score 0.97
HOW TO USE IT
When retrying a job to inspect or continue work on the new job, run `bk job retry <job-id> --json` and use the returned `.id` as the new job UUID for a follow-on command. Use `--text` to print a human-readable confirmation.
retry_uuid=$(bk job retry "<original-job-uuid>" --json | jq -r '.id')
bk job log "$retry_uuid"bk job retry "<original-job-uuid>" --textWHY THIS HELPS
When retrying a job to inspect or continue work on the new job, retrieve its UUID from structured output and pass it to a follow-on command.
BEFORE THIS CHANGE
`bk job retry` returned a success message and URL, so callers had to parse the URL or rediscover the new job.
REQUIREMENTS AND LIMITATIONS
- Version: v3.57.0
- <job-id> (required): UUID of the job to retry.
- --json: Output as JSON; the documented example reads the new job UUID from `.id`.
- --yaml: Output as YAML.
- --text: Output as text; documented as a human-readable confirmation.
- -o, --output: Select output format: `json`, `yaml`, or `text`.
- jq -r '.id': Extract the new job UUID from the JSON output in the documented example; requires `jq` in the shell.
- Prerequisite: Install the Buildkite CLI and configure it with an API access token and organization.
- Prerequisite: The CLI requires an API access token; the documentation does not specify a retry-specific scope.
- JSON is the default output format.
FIRST-PARTY EVIDENCE
- https://github.com/buildkite/cli/releases/tag/v3.57.0
- https://github.com/buildkite/cli/pull/993
- https://buildkite.com/docs/platform/cli/reference/job
- https://buildkite.com/docs/platform/cli/configuration
Check the installed version and the source before using it. Entry JSON