Use AppBarn with your build pipeline
Run appbarn upload after your pipeline exports an IPA, APK or AAB. The same CLI works in Fastlane lanes, Jenkins pipelines and the CI services below. You do not need a provider-specific AppBarn plugin.
Prerequisites
- Install Node.js 22+ and
appbarn-clion the runner. - Store
APPBARN_TOKENin the runner's secret store. Never put it in source control or command arguments. - Set the target App and Environment IDs. Use an Automation Token scoped to that target.
- Make the finished artifact available to the upload step.
Steps
sh
npm install --global appbarn-cli
appbarn config set api https://api.app-barn.com
appbarn config set app "$APPBARN_APP_ID"
appbarn config set environment "$APPBARN_ENVIRONMENT_ID"
appbarn upload "$BUILD_PATH"For APK or AAB files, pass --app-identifier, --version and --build-number. See Upload a build for the full command.
Fastlane and Jenkins
In Fastlane, add the CLI commands after the lane produces its export artifact. In Jenkins, run them in a shell step after the build and supply APPBARN_TOKEN from Jenkins Credentials. In both cases, point BUILD_PATH at the actual output file.
Fastlane and Jenkins can run the CLI, but they are not separate automatic provenance providers. AppBarn detects provider provenance for the five CI services below. Otherwise, the build uses local provenance.
CI setup guides
Expected result
The CLI prints a ready Build with its identity and checksum.
Common failures
Check the artifact path, token scope and build identity if the upload fails. See upload troubleshooting.