gplay tracks create
Create a custom closed-testing track named <name>.
The create endpoint supports exactly one type (CLOSED_TESTING) and the DEFAULT (phone) form factor, so there is no --type / --form-factor flag — every created track is closed. Open / internal track creation has no API path. Creating a track that already exists surfaces the API error (exit 30); gplay does not fake idempotency.
Runs inside an implicit Edit (open → tracks.create → commit). --dry-run previews the TrackConfig without any HTTP; --keep-edit-on-failure skips the auto-discard cleanup on failure (debug). No --confirm: a closed test track is low-stakes and reversible.
gplay tracks create <name> [flags]| Flag | Description |
|---|---|
--dry-run | validate inputs and preview the TrackConfig without any HTTP call |
--keep-edit-on-failure | skip the auto-discard cleanup on failure (debug) |
--output string | output format: table, json, or markdown (default: auto — table on TTY, json in pipes/CI) |
--package string | Android package name (overrides .gplay/config.json pin) |
Global flags
Section titled “Global flags”| Flag | Description |
|---|---|
--account string | name of a stored Account to use (overrides env and active Account) |
--retry int | retry transient failures (transport errors, 5xx, 429) up to N times with exponential backoff (default: 0, no retry) |
--service-account string | path to a service-account JSON, or inline JSON content (overrides --account, env, and active Account) |
--timeout duration | per-request API timeout, e.g. 30s or 2m (default: 60s for control-plane calls, none for uploads) |
-v, --verbose | log flow steps to stderr (info level) |