buildify-publish-cli 1.0.1

CLI for Buildify bundle publish server (machine Bearer auth)

buildify-publish-cli

Command-line client for the Buildify bundle publish HTTP API. Use it to check health, validate publish keys, query bundle metadata, and upload JAR bundles from your terminal or CI.

Requires: Python 3.10 or newer.

Install

From PyPI:

pip install buildify-publish-cli

Other installers:

pipx install buildify-publish-cli
uv tool install buildify-publish-cli

After install, the command is buildify-publish.

Authentication

The API uses Bearer credentials: Authorization: Bearer <keyId>.<secret>.

Set the full secret (both parts after Bearer) as:

• Environment variable BUILDIFY_PUBLISH_API_KEY, or
• buildify-publish config set-api-key (reads from stdin — avoids putting the secret on the command line).

Publish keys are created and rotated in the Buildify console, not through this CLI.

Quick start

export BUILDIFY_PUBLISH_API_KEY='yourKeyId.yourSecret'

buildify-publish health
buildify-publish key test
buildify-publish bundle info --name 'my/group/plugin'
buildify-publish bundle upload \
  --name 'my/group/plugin' \
  --version '1.0.0-SNAPSHOT' \
  --file ./plugin.jar \
  --overwrite

API base URL

Default: https://publish.buildify.cn

Override for self-hosted or other environments:

export BUILDIFY_PUBLISH_BASE_URL='https://your-publish-host.example.com'
# or per invocation:
buildify-publish --base-url 'https://your-publish-host.example.com' health

Persist locally (writes ~/.buildifyrc):

buildify-publish config set-base-url https://publish.buildify.cn
printf '%s' 'keyId.secret' | buildify-publish config set-api-key
buildify-publish config show

If you previously used ~/.config/buildify/publish.toml, it is still read until ~/.buildifyrc exists; running any config set-* merges into ~/.buildifyrc.

Config file: ~/.buildifyrc (Unix) or %USERPROFILE%\.buildifyrc (Windows). Precedence: CLI flags → environment → config file → default base URL.

Built-in reference

Full Markdown reference (commands, env vars, HTTP mapping, exit codes, JSON schema):

buildify-publish help

Same content ships as usage.md inside the package.

Scripting and CI

Machine-readable output (one JSON object per run):

export BUILDIFY_PUBLISH_JSON=1
buildify-publish --json key test

Environment: BUILDIFY_PUBLISH_BASE_URL, BUILDIFY_PUBLISH_API_KEY, BUILDIFY_PUBLISH_JSON, NO_COLOR.

Global flags: --json, --api-key, --base-url, --quiet.

Developing from source

If you have the Git repository checked out:

cd tools/buildify-publish-cli
python3 -m venv .venv && source .venv/bin/activate
pip install -U pip
pip install .

Run without installing into the environment:

python -m buildify_publish --help

License

Same as the upstream project repository unless stated otherwise.