Mobile CI

MCOE’s Mobile CI platform empowers mobile teams to ship apps faster by automating repetitive workflows, delivering ready-to-use integrations for iOS and Android, accelerating testing cycles, and ensuring consistently high-quality releases. The platform is built on top of three connected systems: Immerse, GitHub, and Bitrise.

Architecture Overview

The Enterprise Mobile CI/CD architecture connects three systems that work together to take your code from commit to production:

Immerse

Immerse is the central hub where teams manage their CI/CD configuration:

• Pipelines — Create and manage mobile pipelines for your applications
• Mobile Pipelines — Pre-configured pipeline templates for React Native, iOS Native, and Android Native projects
• Other Pipelines — Support for Node, Java, Docker Image, and Python projects
• Release Management — Full release lifecycle management through Rollouts

When you create a pipeline in Immerse, it commits shared workflow configuration directly to your GitHub repository.

GitHub

GitHub hosts your application source code and the shared CI workflows:

• Mobile App Projects — Your team’s repositories (e.g., Optum Mobile, Optum RX, UHC Mobile) each receive a shared React Native Workflow
• EPL Workflows — Enterprise Pipeline Library workflows that orchestrate the CI process. The mobile workflow (React Native EPL) calls your .jfrog/config.yml and triggers builds via the Bitrise API
• Other Workflows — Node, Java, Docker, and Python workflow templates for non-mobile projects

Bitrise

Bitrise handles mobile-specific build, test, and release operations:

• Projects — Each application has a Bitrise project containing both Bitrise CI and Release Management

• Workflows — Pre-configured workflows for each build type:

  • iOS Build (Dev / Test / Prod)
  • Android Build (Dev / Test / Prod)
  • Release Candidate
  • Android Native Build
  • iOS Native Build

• Release Management — Enterprise Approvals, App Store Connect integration, and Google Play Store integration

How It All Connects

1. Immerse creates the pipeline

   When you create a mobile pipeline in Immerse, it provisions the necessary Bitrise project and commits shared workflow files to your GitHub repository.

2. GitHub Actions runs the CI workflow

   On push or pull request, the shared React Native CI workflow runs — installing dependencies, running tests, performing code quality scans, and triggering Bitrise builds.

3. Bitrise builds your app

   Bitrise executes the mobile-specific build workflow (iOS/Android), producing signed artifacts (.ipa or .aab files).

4. Artifacts flow back

   Build artifacts are downloaded from Bitrise and can be uploaded to JFrog or used directly in the Release Management pipeline.

5. Release Management takes over

   Once artifacts are ready, the Rollouts module manages the full release lifecycle — testing, approvals, store review, and production release.

Supported Platforms

Getting Started

1. Ensure your project is in Bitrise

   Your application needs a Bitrise project. If you don’t have one yet, the Enterprise Pipelines flow in Immerse will create one for you.

2. Set up your CI workflow

   Add the React Native CI reusable workflow to your repository’s GitHub Actions configuration.

3. Configure Bitrise authentication

   Set up either a Bitrise API token or OIDC-based authentication for secure build triggering.

4. Create a Rollout (optional)

   If you want to manage releases through Immerse, create a Rollout and connect it to your Bitrise project.

What’s Next

• Enterprise Pipelines — Create and manage pipelines in Immerse
• React Native CI Workflow — Configure the reusable CI workflow for your project
• Migrating to Bitrise — Move your existing CI from GitHub Actions to Bitrise
• Release Management — Manage your full release lifecycle