A recipe for a CI/CD pipeline
summary
A complete CI/CD pipeline for the OwnTracks Android app uses CircleCI with Docker and VM executors, Gradle builds, Jacoco + Codecov coverage, and Espresso UI tests sharded into 4 parallel runs on machine images that support nested virtualization. Unit test jobs run in ~1m45s, restore cache takes ~27s, and caching reuses ~1.2 GB to speed builds. Release publishing uses the Gradle Play Publisher with encrypted credentials, forks trigger a reduced OSS flow, and configuration relies on orbs and dynamic YAML parameters.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 1:08Cooking blogs and Android
- 6:21Introducing the pipeline
- 12:59Unit testing and linting
- 18:40UI testing with Espresso
- 24:37Publishing to stores
- 27:05Orchestrating workflows
- 30:59Gradle cache optimization
- 32:23Triggers and schedules
- 33:51Open-source contributions
- 37:04Q&A and closing
related talks
34mPractical tips for succeeding with CI/CD for Android
20mContinuous integration for mobile
53mCI for Android Using Jenkins
25mMobile DevOps - How CI/CD can change your development world
38mCI & CD: CircleCI 2.0 + Intro to Test Tracks
30mCI Recipes and Release Flow Strategies for Medium and Larger Apps
52mFrom Laptop Builds to Advanced CI
43mBetter, Faster, and Stronger CI/CD Pipeline