Buildkite CLI package command
The bk package command allows you to manage packages from the command line.
Commands
| Command | Description |
|---|---|
bk package push |
Push a new package to a Buildkite registry |
Push package
Push a new package to a Buildkite registry. The package can be passed as a path to a file with the --file-path flag, or via stdin. If passed via stdin, the filename must be provided with the --stdin-file-name flag, as a Buildkite registry requires a filename for the package.
bk package push <registry-slug> [<std-in-arg>] [flags]
Arguments
| Argument | Description |
|---|---|
<registry-slug> |
The slug of the registry to push the package to |
[<std-in-arg>] |
Use '-' as value to pass package via stdin. Required if --stdin-file-name is used. |
Flags
| Flag | Description |
|---|---|
-w, --web
|
Open the pipeline in a web browser. |
--debug |
Log HTTP API traffic to stderr; bodies may contain sensitive data |
--file-path=STRING |
Path to the package file to push |
--org=STRING |
Organization slug for this invocation (overrides environment and configuration) |
--stdin-file-name=STRING |
The filename to use when reading the package from stdin |
Examples
Push package from file:
bk package push my-registry --file-path my-package.tar.gz
Push package via stdin:
cat my-package.tar.gz | bk package push my-registry --stdin-file-name my-package.tar.gz - # Pass package via stdin, note hyphen as the argument
add -w to open the build in your web browser:
bk package push my-registry --file-path my-package.tar.gz -w