b8e build upload
Upload a .apk, .aab, .ipa or .app build to a mobile project, register it as a build and start its malware scan
Arguments
Section titled “Arguments”| Argument | Arity | Default | Description |
|---|---|---|---|
file | required | the build file: .apk or .aab for android, .ipa or .app for ios |
Options
Section titled “Options”| Option | Takes | Default | Description |
|---|---|---|---|
--release <release> | value | the build’s release, e.g. 2.0.1 | |
--dist <dist> | value | the build’s dist (build number), e.g. 2000051 | |
--project <id> | value | project (default: the one b8e project selected) |
b8e build upload --help
Section titled “b8e build upload --help”Identical to what the terminal prints — both are rendered from the same commander definition.
Usage: b8e build upload [options] <file>
Upload a .apk, .aab, .ipa or .app build to a mobile project, register it as abuild and start its malware scan
Arguments: file the build file: .apk or .aab for android, .ipa or .app for ios
Options: --release <release> the build's release, e.g. 2.0.1 --dist <dist> the build's dist (build number), e.g. 2000051 --project <id> project (default: the one `b8e project` selected) -h, --help display help for command
stdout carries one line, "<release>/<dist> <build target id>"; progress goes to stderr.The build registers in the production environment, as `b8e audit --build-target` does.
EXAMPLES $ b8e build upload app-release.apk --release 2.0.1 --dist 2000051 $ b8e build upload App.ipa --release 1.4.0 --dist 137 --project prj_123
INHERITED FLAGS --org <id|slug|name> organization context [$BINCLUSIVE_ORG_ID] -y, --yes skip all prompts and accept defaults --non-interactive never prompt; fail instead of asking --progress <mode> how progress is reported -q, --quiet suppress progress output (same as --progress quiet) --no-color disable color -v, --verbose verbose diagnostics -V, --version print the CLI version -h, --help show help for command