CI Builds

Patterns for getting your app binary into Revyl from any CI system.

Pattern 1: Upload from a URL (simplest)

If your build system produces a downloadable artifact URL (EAS, Bitrise, AppCenter, S3, GCS, GitHub Actions artifacts) then you can skip the local download entirely. The Revyl backend downloads the artifact from the URL, validates, and stores the artifact server-side using this command:

revyl build upload --url https://your-ci.com/artifacts/app-latest.apk --app "My Android App"

For authenticated URLs:

revyl build upload \
  --url https://artifacts.internal.company.com/builds/app.ipa \
  --header "Authorization: Bearer $ARTIFACT_TOKEN" \
  --app "My iOS App"

Pattern 2: Revyl CLI in GitHub Actions

Use the CLI after your workflow builds the app. In GitHub Actions, pass the PR head SHA as the build version so Revyl can match the artifact back to the pull request.

- name: Install Revyl CLI
  run: curl -fsSL https://revyl.com/install.sh | sh

- name: Upload Build
  id: upload
  run: |
    revyl build upload \
      --file ./build/app.apk \
      --app "$REVYL_ANDROID_APP_ID" \
      --platform android \
      --version "$REVYL_PR_HEAD_SHA" \
      --yes \
      --json
  env:
    REVYL_API_KEY: ${{ secrets.REVYL_API_KEY }}
    REVYL_ANDROID_APP_ID: ${{ vars.REVYL_ANDROID_APP_ID }}
    REVYL_PR_HEAD_SHA: ${{ github.event.pull_request.head.sha || github.sha }}

- name: Run Tests
  run: revyl workflow run smoke-tests --android-app "$REVYL_ANDROID_APP_ID"
  env:
    REVYL_API_KEY: ${{ secrets.REVYL_API_KEY }}
    REVYL_ANDROID_APP_ID: ${{ vars.REVYL_ANDROID_APP_ID }}

Pattern 3: Build on CI, Upload File

Build on the runner and upload the artifact directly:

curl -fsSL https://revyl.com/install.sh | sh
export PATH="$HOME/.revyl/bin:$PATH"
revyl build upload --file ./build/app.apk --platform android --yes
revyl workflow run smoke-tests

iOS on macOS runners

jobs:
  test:
    runs-on: macos-latest
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: |
          bun install
          bunx expo prebuild --platform ios
          cd ios && pod install
          cd ios && xcodebuild -workspace YourApp.xcworkspace -scheme YourApp -configuration Release -sdk iphonesimulator -destination 'generic/platform=iOS Simulator' -derivedDataPath build ARCHS=arm64
      - env:
          REVYL_API_KEY: ${{ secrets.REVYL_API_KEY }}
        run: |
          curl -fsSL https://revyl.com/install.sh | sh
          export PATH="$HOME/.revyl/bin:$PATH"
          revyl build upload --file ios/build/Build/Products/Release-iphonesimulator/*.app --platform ios --yes
          revyl workflow run smoke-tests

GitHub Actions includes macOS runners on all paid plans.

Android on Linux runners

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: |
          bun install
          bunx expo prebuild --platform android
          cd android && ./gradlew assembleRelease
      - env:
          REVYL_API_KEY: ${{ secrets.REVYL_API_KEY }}
        run: |
          curl -fsSL https://revyl.com/install.sh | sh
          export PATH="$HOME/.revyl/bin:$PATH"
          revyl build upload --file android/app/build/outputs/apk/release/*.apk --platform android --yes
          revyl workflow run smoke-tests

Pattern 4: EAS Cloud + URL Upload (no Mac, no local build)

For Expo teams, delegate the build to EAS and just ingest the result:

ARTIFACT_URL=$(npx eas-cli build --profile development --platform ios --non-interactive --json | jq -r '.[0].artifacts.buildUrl')
revyl build upload --url "$ARTIFACT_URL" --app "My iOS App"

The EAS command requires Expo authentication; use EXPO_TOKEN for unattended CI. The Revyl upload separately requires REVYL_API_KEY. Zero Mac is needed on the customer side: Expo’s cloud does the build, and Revyl ingests the artifact.

Pattern 5: revyl build (config-driven)

If .revyl/config.yaml has build commands configured, the CLI can build and upload in one step:

revyl build --profile release --platform ios --json

This resolves exactly one named profile/platform recipe, runs its setup_commands followed by build_commands, then resolves and uploads output_path. CI should always configure app_id and pass --profile and --platform explicitly so configuration growth cannot make selection ambiguous. To run that same recipe on a Revyl cloud runner instead of the CI machine:

revyl build --profile release --platform ios --remote --json

Pattern 6: Preview URL (no device at upload time)

--preview prints a URL that auto-starts a simulator with that exact build when a signed-in org member opens it. Upload itself does not start a device.

revyl build upload --file android/app/build/outputs/apk/release/*.apk \
  --platform android --yes --preview --json

--json stays the same envelope and adds optional preview_url on the build object (/sessions/launch?buildId=<id>). Post that URL on the PR. Opening it starts a simulator and opens the normal session viewer. The launch page reads platform from the uploaded build’s app. Refreshing /sessions/launch while a start is in flight opens the same session. After that start settles, opening the durable preview URL again starts a new device. Refreshing the live session does not start another device. For a link that always opens the app’s most recent build instead of one pinned upload, use /sessions/launch?appId=<app_id>. The latest build is resolved each time the link is opened, so one iOS link and one Android link (one per app) stay current as CI uploads new builds. Copy this link from the Apps page row menu (“Copy preview link”).

CI-Friendly Flags

Flag	Effect
`--json`	Machine-readable JSON output
`--preview`	Emit a `preview_url` that auto-starts a simulator when opened
`--no-wait`	Queue the run and exit without waiting for results
`--quiet` / `-q`	Suppress non-essential output
`--version <string>`	Tag the build with a version (default: `<branch>-<timestamp>`)

Next Steps

Expo Build Guide — Expo-specific build and upload
CI/CD Integration — full CI pipeline setup

Getting Started

CLI

Builds

Tests

Develop

Atlas

Integrations

Appendix

Pattern 1: Upload from a URL (simplest)

Pattern 2: Revyl CLI in GitHub Actions

Pattern 3: Build on CI, Upload File

iOS on macOS runners

Android on Linux runners

Pattern 4: EAS Cloud + URL Upload (no Mac, no local build)

Pattern 5: revyl build (config-driven)

Pattern 6: Preview URL (no device at upload time)

CI-Friendly Flags

Next Steps

​Pattern 1: Upload from a URL (simplest)

​Pattern 2: Revyl CLI in GitHub Actions

​Pattern 3: Build on CI, Upload File

​iOS on macOS runners

​Android on Linux runners

​Pattern 4: EAS Cloud + URL Upload (no Mac, no local build)

​Pattern 5: revyl build (config-driven)

​Pattern 6: Preview URL (no device at upload time)

​CI-Friendly Flags

​Next Steps

Pattern 1: Upload from a URL (simplest)

Pattern 2: Revyl CLI in GitHub Actions

Pattern 3: Build on CI, Upload File

iOS on macOS runners

Android on Linux runners

Pattern 4: EAS Cloud + URL Upload (no Mac, no local build)

Pattern 5: revyl build (config-driven)

Pattern 6: Preview URL (no device at upload time)

CI-Friendly Flags

Next Steps