Release Management
Getting Started with Rollouts
Overview of the Rollouts module, key concepts, prerequisites, and how to access it.
The Rollouts module in Immerse helps you manage mobile app releases from build selection through App Store submission and production release. It provides a structured pipeline with built-in compliance checks, approval workflows, and integration with Bitrise CI/CD and Apple App Store Connect.
Your project must be fully migrated to Bitrise CI before using Rollouts. If you haven’t migrated yet, see Migrating from GitHub to Bitrise.
What Is a Rollout?
A rollout is a container that represents a mobile application’s release process. Each rollout is tied to a specific application (identified by its ASK ID) and holds:
- Configuration — App Store Connect and Google Play Console settings
- Versions — Individual releases that move through the pipeline
- Approvals — Compliance and business sign-offs required before release
- Connected Apps — Links to your Bitrise CI projects
Think of a rollout as the “home base” for all releases of a particular mobile app.
Key Concepts
Version
A version represents a single release (e.g., v1.2.6). Each version moves through a 5-stage pipeline from build selection to production release. You can have multiple versions for the same rollout, each at different stages.
Pipeline Stages
Every version passes through these stages in order:
See Pipeline Overview for details on each stage.
Approvals
Six approval types are required before a version can be submitted for App Store review:
| Type | Category | Description |
|---|---|---|
| OSPO | Compliance | Automated open-source license scan |
| Legal | Compliance | Legal review and sign-off |
| ESRO | Compliance | Export/sanctions compliance review |
| Service Owner | Business | Sign-off from the service owner |
| Technical Owner | Business | Sign-off from the technical lead |
| Product Owner | Business | Sign-off from the product manager |
See Approvals for the full approval workflow.
Connected Apps
A connected app is a Bitrise project linked to your rollout. Connected apps provide the build artifacts (.ipa or .apk files) that become your release candidates. Each connected app has a platform (iOS or Android).
Prerequisites
Before using the Rollouts module, make sure you have:
-
An application registered in Immerse
Your application must have a valid ASK ID in the Immerse application registry.
-
A Bitrise CI project
Your application’s source code repository must be connected to a Bitrise CI project. If you haven’t migrated yet, see Migrating from GitHub.
-
App Store Connect access (iOS)
For iOS releases, your team must be configured in App Store Connect with the necessary API key credentials.
-
Appropriate permissions
You need permissions to create rollouts and manage versions in Immerse.
Accessing the Rollouts Module
-
Open Immerse Platform
Navigate to Immerse Platform and sign in with your credentials.
-
Go to Rollouts
From the left navigation sidebar, select Rollouts.
From here you’ll see all Rollouts created by your team, or the option to create your first one. The Rollouts module is located at /beta/rollouts/ in the portal.
Your First Rollout — Quick Path
-
Create a Rollout
Create a Rollout to link your application.
-
Complete the Checklist
Complete the Setup Checklist to configure required settings.
-
Configure Settings
Add App Store Connect details and other platform-specific configuration.
-
Create a Version
Create your first version to start a release.
-
Work through the pipeline
Move through the pipeline stages — Build, Test, Approve, Review, Release.