Favicon

You are here: Home > App Distribution > CI/CD > Bitrise

Bitrise

Learn how to integrate Applivery with Bitrise CI/CD for automated mobile app building, testing, and deployment. Streamline your workflow with this guide.

10 min read

TL;DR

Integrate Applivery with Bitrise to automate mobile app deployment by using the Applivery Step in your Bitrise workflow.

bitrise

Bitrise is a mobile-first CI/CD platform designed specifically for iOS and Android app development. It uses Workflows — sequences of configurable Steps — to automate building, testing, signing, and deploying apps.

Applivery has an official Applivery Step in the Bitrise Step Library. Adding it to your workflow automatically uploads the built binary to Applivery after each successful build, with full CI metadata (branch, commit, build number) attached.

Prerequisites

Before setting up the integration, make sure you have:

  • A Bitrise.io account with an app already connected to your repository (GitHub, GitLab, or Bitbucket).
  • An Applivery App API Token. Find it in App Settings → API Tokens in the Applivery dashboard, or see Apps API Token.
1
Store the App Token as a Bitrise Secret

Never paste your token directly into a Step input field — it would be visible in your workflow configuration. Store it as a Secret so it is masked in logs and injected as an environment variable.

  1. Open your Bitrise app and go to the Secrets tab (top navigation).
  2. Click Add new.
  3. Set the key to APPLIVERY_APP_TOKEN.
  4. Paste your Applivery App API Token as the value.
  5. Enable Protected to prevent the value from being exposed in build logs.
  6. Click Save.

Once saved, you can reference it anywhere in your workflow as $APPLIVERY_APP_TOKEN.

2
Add the Applivery Step to your workflow
  1. Open your Bitrise app and go to the Workflows tab.
  2. Select the workflow where you want to add the Applivery deployment (typically your main build workflow, e.g. primary or deploy).
  3. Click the + button at the point in the workflow where you want to add the Step — place it after your build and signing steps (e.g., after Xcode Archive & Export for iOS or Android Build).
  4. In the Step search box, type Applivery.
  5. Select the Deploy to Applivery step from the results and click Add.
3
Configure the Applivery Step

With the Step added to your workflow, click on it to open its configuration panel. Fill in the following fields:

Required

Field Value
App Token $APPLIVERY_APP_TOKEN (references the secret you created in Step 1)

Optional

Field Description
Build name Human-readable label for the build. You can use Bitrise environment variables like $BITRISE_BUILD_NUMBER or $GIT_CLONE_COMMIT_MESSAGE_SUBJECT.
Changelog Release notes for this build. Use $GIT_CLONE_COMMIT_MESSAGE_BODY to pull in the commit message automatically.
Tags Comma-separated tags to label the build in Applivery. E.g. bitrise, staging.
Notify Collaborators Set to true to send an email notification to app collaborators after the upload.
Notify Employees Set to true to send an email notification to store employees.
Notify Message Custom message to include in the notification email.
Build path Path to the binary to upload. If left empty, the Step automatically uses the output from the preceding build step ($BITRISE_IPA_PATH for iOS or $BITRISE_APK_PATH for Android).
4
Run your workflow

Trigger a build manually to verify the integration:

  1. In your Bitrise app, click Start/Schedule a build.
  2. Select the workflow you configured.
  3. Click Start Build.

Once the build completes, the Applivery Step will upload the binary to your Applivery app. Open the Applivery dashboard to confirm the build appears with the correct metadata.

Bitrise Environment Variables

The Applivery Step automatically captures Bitrise CI metadata. You can also reference these variables explicitly in Step input fields:

Variable Description
$BITRISE_BUILD_NUMBER Sequential build number assigned by Bitrise.
$BITRISE_BUILD_URL Direct URL to the current build in the Bitrise dashboard.
$BITRISE_GIT_BRANCH The Git branch that triggered the build.
$BITRISE_GIT_COMMIT The Git commit SHA that triggered the build.
$BITRISE_GIT_TAG The Git tag, if the build was triggered by a tag push.
$GIT_CLONE_COMMIT_MESSAGE_SUBJECT The first line of the commit message.
$GIT_CLONE_COMMIT_MESSAGE_BODY The full commit message body.
$BITRISE_IPA_PATH Path to the exported .ipa file (iOS builds).
$BITRISE_APK_PATH Path to the generated .apk file (Android builds).

For the full list of Bitrise environment variables, see the Bitrise CLI documentation.

Using Fastlane with Bitrise

If your project already uses Fastlane, you can combine Bitrise with the Applivery Fastlane plugin instead of using the dedicated Applivery Step. Add a Fastlane Step to your workflow and invoke the lane that calls the applivery action:

Step: Fastlane
Lane: ios deploy

In this setup, pass the token via a Bitrise Secret referenced as $APPLIVERY_APP_TOKEN and read it in your Fastfile as ENV["APPLIVERY_APP_TOKEN"].

See the Fastlane Integration guide for full Fastfile configuration.

Key Takeaways

  • Automate mobile app deployment with Applivery and Bitrise.
  • Store Applivery API token as a secret in Bitrise.
  • Use the Applivery Step in your Bitrise workflow.
  • Configure the Applivery Step with required parameters.
  • Leverage Bitrise environment variables for dynamic configuration.