QuollVault Docs

Appearance

Quick start ​

Use QuollVault to upload one build and confirm it is retained outside CI.

Prerequisites ​

  • a QuollVault Workspace, Project, App and Environment;
  • an Automation Token scoped to the target Project or App;
  • Node.js 22+ until the packaged CLI release in F19.

Steps ​

  1. Configure the API and target resources:
sh
quollvault config set api https://api.quollvault.com
quollvault config set project <project-uuid>
quollvault config set app <app-uuid>
quollvault config set environment <environment-uuid>
  1. Export the token without putting it in command history:
sh
export QUOLLVAULT_TOKEN='<automation-token>'
  1. Upload an IPA, APK or AAB:
sh
quollvault upload ./build/app.apk
  1. List retained builds:
sh
quollvault builds list

Expected result ​

The upload returns a ready Build with parsed identity, SHA-256 and provenance. builds list returns the same Build.

Common failures ​

  • 401: token missing, expired or revoked — create/use a current Automation Token.
  • 403/404: token scope or current App Manager authority does not cover the target — verify Workspace/Project/App selection.
  • 409: idempotency or lifecycle conflict — do not reuse an upload identity for different bytes.
  • 413: artifact exceeds the 2 GiB upload cap.
  • 429: Workspace quota is exhausted — remove retained data or request more capacity.