Archive IPA, APK and AAB builds from CI

Add an AppBarn upload step after your existing build job creates its artifact. AppBarn does not replace your CI runner, Xcode, Android Studio or signing process.

What to add

1. Have your CI job export a completed IPA, APK or AAB artifact.
2. Install the official appbarn-cli using Node.js 22+ on the runner.
3. Provide APPBARN_TOKEN through the runner's secret store, never in source code.
4. Configure your target App and Environment IDs and upload the artifact.
5. Check the ready Build identity and SHA-256 checksum after upload. Complete CI workflow.

Example: A GitHub Actions Android job builds an APK, then uses the GitHub Actions guide to upload that same APK to AppBarn. QA can later retrieve the version even when the job's original artifact expires.

Supported integrations and limits

The same CLI works in GitHub Actions, GitLab CI, Azure Pipelines, Bitrise and Codemagic. Fastlane and Jenkins can call the CLI without separate AppBarn integrations. Only the five named CI providers have automatic provenance detection. CI overview.

AppBarn stores uploaded binaries, not source trees. It does not rebuild, sign or publish an app. Each upload is subject to the 2 GiB file maximum and Workspace limits. Artifacts and limits.

Upload commands · Automation Tokens · Provenance