Buildkite CLI artifacts command

The bk artifacts command allows you to manage build artifacts from the command line.

Commands

Command Description
bk artifacts download Download artifacts from a build.
bk artifacts list List artifacts for a build or a job in a build.

Download an artifact

Download artifacts from a build.

bk artifacts download [<artifact-id>] [flags]

Arguments

Argument Description
[<artifact-id>] Artifact ID to download. If omitted, all matching artifacts are downloaded (see --path/--state). Use 'bk artifacts list' to find IDs.

Flags

Flag Description
-b, --build=STRING Build number containing the artifact. If omitted, the most recent build on the current branch will be used.
-j, --job-uuid=STRING The job UUID containing the artifact.
-p, --pipeline=STRING The pipeline containing the artifact. This can be a {pipeline slug} or in the format {org slug}/{pipeline slug}. If omitted, it will be resolved using the current directory.
--debug Enable debug output for REST API calls
--path=STRING Filter artifacts by path. Supports exact matches and glob patterns using * as a wildcard, for example --path "log/rspec*.json".
--state=STRING Filter artifacts to download by state. Must be one of: new, finished, error, deleted, expired.

Examples

Download all artifacts from the most recent build on the current branch:

bk artifacts download

Download all artifacts from a specific build:

bk artifacts download --build 429

Download all artifacts from a specific job:

bk artifacts download --build 429 --job-uuid 0193903e-ecd9-4c51-9156-0738da987e87

Download a specific artifact:

bk artifacts download 0191727d-b5ce-4576-b37d-477ae0ca830c --build 429

Specify the pipeline explicitly:

bk artifacts download --build 429 -p monolith

Filter artifacts to download by path or state:

bk artifacts download --build 429 --path "log/rspec*.json"
bk artifacts download --build 429 --state finished

List artifacts

List artifacts for a build or a job in a build.

bk artifacts list [<build-number>] [flags]

Arguments

Argument Description
[<build-number>] Build number to list artifacts for

Flags

Flag Description
-j, --job-uuid=STRING List artifacts for a specific job on the given build.
-o, --output="" Output format. One of: json, yaml, text
-p, --pipeline=STRING The pipeline to view. This can be a {pipeline slug} or in the format {org slug}/{pipeline slug}. If omitted, it will be resolved using the current directory.
--debug Enable debug output for REST API calls
--path=STRING Filter artifacts by path. Supports exact matches and glob patterns using * as a wildcard, for example --path "log/rspec*.json".
--path=STRING Filter artifacts by path. Supports exact matches and glob patterns using * as a wildcard, for example --path "log/rspec*.json".
--state=STRING Filter artifacts by state. Must be one of: new, finished, error, deleted, expired.
--text Output as text
--yaml Output as YAML

Examples

By default, artifacts of the most recent build for the current branch is shown:

bk artifacts list

To list artifacts of a specific build:

bk artifacts list 429

To list artifacts of a specific job in a build:

bk artifacts list 429 --job-uuid 0193903e-ecd9-4c51-9156-0738da987e87

If not inside a repository or to use a specific pipeline, pass -p:

bk artifacts list 429 -p monolith

Filter artifacts by path or state:

bk artifacts list 429 --path "log/rspec*.json"
bk artifacts list 429 --state finished