Solutions / Android
Android CI/CD: build, test and ship Android apps faster
Android CI/CD automatically builds, tests and releases your app on every push. Semaphore runs Gradle, React Native and Flutter pipelines on fast Linux machines with the Android SDK ready to go, so your team can release multiple times a day without waiting on builds.
Projects
Native Android, React Native, Flutter
Environment
Linux + Android SDK image
Deploy to
Google Play and more
Pricing
Per second, no seats
TL;DR
- Semaphore’s Android CI/CD runs Gradle builds and tests in a ready-made Android image that scales with every push.
- Native Android, React Native and Flutter projects, with pipelines kept as code or built in the visual Workflow Builder.
- Parallel jobs and smart caching for fast feedback; rerun workflows or SSH into a job to debug.
- Sign and ship to Google Play from a promotion, and run your iOS and web pipelines on the same platform.
How Android CI/CD works on Semaphore
01
Push to Git
Semaphore starts a pipeline in a clean Android build environment.
02
Build and test
Gradle builds the app; unit and lint jobs run in parallel with cached dependencies.
03
Sign and ship
A promotion signs the release and uploads it to Google Play.
Example Android CI/CD pipeline
Run unit tests and lint in parallel in the Semaphore Android image, then promote passing builds on main to Google Play.
.semaphore/semaphore.yml
version: v1.0
name: Android CI/CD
agent:
machine:
type: f1-standard-2
os_image: ubuntu2404
containers:
- name: main
image: 'registry.semaphoreci.com/android:36'
blocks:
- name: Test
task:
prologue:
commands:
- checkout
- cache restore
jobs:
- name: Unit tests
commands:
- ./gradlew testDebugUnitTest
- name: Lint
commands:
- ./gradlew lintDebug
epilogue:
always:
commands:
- cache store
promotions:
- name: Google Play
pipeline_file: play-store.yml
auto_promote:
when: "branch = 'main' AND result = 'passed'"
More options, including emulators for UI tests: Android docs.
What’s included in Semaphore Android CI/CD
Native or cross-platform builds
Fine-tuned environments for Android, React Native and Flutter projects. Android docs
All projects in one place
Run your Android, iOS and web projects on a single CI/CD platform. iOS CI/CD
Scale on demand
Semaphore scales to run on every git push, and you only pay for what you use. Cloud CI/CD
Templates and a visual builder
Start from Android pipeline templates and fine-tune them in the Workflow Builder. Workflow builder
Parallel jobs and caching
Run jobs in parallel with smart caching for fast feedback. Build optimization
Debug in seconds
Rerun finished workflows instantly or SSH into running jobs. SSH debugging
Ship to app stores
Sign and deploy Android or iOS apps to Google Play, the App Store and more. Promotions
Configuration as code
Pipelines are versioned with your repository, alongside your app.
Faster Android builds after switching
“We migrated our CI from Travis to Semaphore. Travis Android build took 12 minutes, now 7 minutes with Semaphore. We are very happy, this far exceeds our expectations!”
Timo Mämecke, Software Engineer at Railslove
Customer reviews
“Semaphore helped us reduce our CI/CD pipelines to under 10 minutes on average.”
Mike Voets, Full Stack Engineer at Optimal Workshop
“We perform 10+ releases a day and have not had any problems.”
Fredrik A. Madsen-Malmo, Senior Product Engineer at Kvist
“Cuts our feedback loop significantly and improves developer productivity.”
Clément Joubert, CEO at levups
CI/CD for other platforms
FAQs
Android CI/CD is continuous integration and delivery for Android apps: every push automatically builds the app with Gradle, runs unit, lint and UI tests, signs the release and delivers it to Google Play or testers. Semaphore runs these pipelines in a ready-made Android build environment.
Yes. Semaphore has environments for native Android, React Native and Flutter projects, and you can run their iOS builds on the same platform.
Yes. You can install SDK platforms and system images with sdkmanager and create an emulator in your job. The Android docs show the setup.
Store your signing key and Play Console credentials as encrypted secrets, then add a promotion that signs the release and uploads it, for example with Fastlane.
Cache Gradle dependencies between runs with the cache command, split tests and lint into parallel jobs, and pick a faster machine type for heavy builds.
Next steps
Start Android CI/CD free · Android docs · Machine types · Pricing
From the blog