Advanced Workflows for Multi-Platform Mobile Development
summary
A CI setup for a mobile library that shares a C++ core with Objective‑C/Swift bindings and a JNI Android layer, uses Jenkins to run make/clang/xcodebuild and Gradle, stores artifacts on S3, and runs Valgrind and unit tests across Mac, Linux and Windows slaves. Pipelines use the build‑flow plugin with trigger jobs to avoid GitHub rate issues, many small jobs orchestrated into release graphs, extreme-feedback lights for broken masters, and strict practices like fingerprint your artifacts and defensive release scripts.
AI-written summary · about
chapters (23)
- 0:00Start
- 0:33About Me
- 3:25Example apps!
- 3:49Layers: Cocoa edition
- 4:36Layers: Android edition
- 5:38Luckily for us Jenkins is amazing
- 6:34One co-located team working on a dozen different projects
- 7:19Tip #1
- 7:55Fast-feedback on Pull Requests
- 8:40Test Master... Hard
- 10:06Extreme Feedback!
- 12:09One of our pipelines
- 12:47It's a simple pipeline
- 13:15Tip #2
- 13:48Several teams spread across CPH and SFO
- 14:39Tip #3
- 15:39One of our release pipelines
- 15:59Imports
- 16:42Retrieve your data
- 18:29Be defensive - Part 2
- 18:39Execute!
- 18:53Tip #4
- 21:31One big job or several small ones?
related talks
22mAdvanced Workflows for Multi-Platform Mobile Development
36mPutting together the best CI workflow for mobile apps
20mContinuous integration for mobile
16mMobile CI Server with GitLab CI and Fastlane
46mAutomatic Deployment of iOS and/or Android Apps
24mMobile development process automation
39mMobile DevOps - From Idea to App Store
05mSet it and forget it!