โ
Loading release pipeline status...
Release Audit Trail & Play Store Events
Chronological ledger of API calls, Google reviews, and policy checks
| Application | Package Name | Active Track | Internal | Closed (Alpha) | Open (Beta) | Production | Actions |
|---|
1. Application Identity
General metadata and workspace package identification.
2. Google Play Service Account Credentials
Authenticated credentials used for automated multi-track promotion and Android Vitals SLA monitoring.
This service account is authorized to manage releases and monitor Android Vitals for this application package.
Release Manager permission assigned in Google Play Console โ Users & Permissions for this specific package.3. Track Progression & Soak Durations
Configure minimum bake times and rollout stages before automated promotion.
Internal Testing Track
CI/CD artifact ingestion & preliminary team testing soak
Closed Testing (Alpha) Track
Internal โ Alpha private tester pool soak
Open Testing (Beta) Track
Public community testing soak before entering Production rollout
Production Staged Rollout
Gradual percentage rollout (10% โ 50% โ 100%) with inter-stage bake
4. Android Vitals & SLA Circuit-Breakers
Optional real-time health gating powered by Google Play Developer Reporting API.
โก Google Play Reporting API (Android Vitals)
Initial onboarding only requires standard Publishing permissions. When enabled, AutoPromote queries Google Play Reporting API (playdeveloperreporting.googleapis.com) to ingest live daily crash metrics and halt rollouts if crash rates fall below SLA.
5. CI/CD Pipeline Ingestion
Trigger automated release workflows directly from your CI runner upon build upload.
Authorization: Bearer $AUTOPROMOTE_TOKEN. Store it as a CI secret named AUTOPROMOTE_TOKEN.apt_โขโขโขโขโขโขโขโขโขโขโขโขโขโขโขโขConnect New Android Application
Configure automated multi-track promotion in 4 straightforward steps.
1. Application Details
Provide identifying information for your Android application.
Release v3.12.0 (Build 1084)
Soaking in Closed Testing (Alpha). Next track: Open Testing (Beta).
Release Execution Event Ledger
4 events loggedAll Release Runs
Click any row below to inspect its full pipeline flow and execution metrics
| Version Code & Name | App | Current Track | Started / Completed | Testers | Crash SLA | Run Status | Action |
|---|
Post rich release cards with approval actions directly into #release channels.
Deliver adaptive cards and stage completion alerts to engineering teams.
Trigger high-urgency incidents when crash SLAs breach or emergency halts fire.
Send signed HMAC JSON payloads to Datadog, Grafana, or internal services.
Configured Broadcast Channels
Active routing destinations listening for multi-track release events
| Channel & Destination | Type | Subscribed Events | Status | Last Fired | Actions |
|---|
Available Release Lifecycle Broadcast Events
Dispatched when CI/CD finishes uploading a new version to the draft/internal track.
Fired when Google Play edits commit and an app moves to Alpha, Beta, or Production.
Triggered when Play Console confirms review passed without policy violations.
Notifies release team that the required 24h/48h soak interval passed with clean SLA.
Triggered if crash-free rate falls below policy (e.g. < 99.50%) during rollout.
Dispatched immediately when an engineer triggers the circuit breaker halt.
Public CI/CD Trigger Endpoint
Call this URL from your GitHub Actions / GitLab pipeline upon successful upload of the AAB to Google Play
Ingested Webhook Requests
Chronological ledger of incoming HTTP triggers and payload validation
| Request ID & CI Provider | Target Application | Version Code / Name | Triggered Workflow | Status & Latency | Timestamp | Action |
|---|
| Member | Role | Joined | Last Active | Actions |
|---|
Workspace Plan & Billing
Manage your active workspace plan, billing interval, and entitlements.
User Account & Profile
Default Pipeline Steps & Gating Policy
Configure which tracks and soak stages are enabled for Active Application
Promote internal builds to closed testing group first.
Promote to public beta testers before releasing to production.
Gradually ramp release (10% โ 50% โ 100%) instead of immediate full release.
Automatically abort previous in-flight workflow runs when a newer build/versionCode is uploaded.
Pause the pipeline after the last pre-production soak until someone approves the production rollout.