Automating Daily Builds for 400 App Variants
summary
Yappli’s build automation for iOS/Android generates distinct projects from CMS settings and automatically builds, code-signs, and uploads apps to the App Store or Google Play. The talk explains challenges encountered when scaling daily builds for about 400 different apps—such as manual project edits, correct bundle IDs and versions, placement of signing and push notification resources—and the technical solutions used to automate and robustly handle those issues.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:57What is Build and Submission Work?
- 2:28Existing Workflow and Stakeholders
- 4:51Organizing Challenges
- 6:42Purpose and Goals of Automation
- 7:22An Even More Ideal Workflow
- 7:59Build Work
- 10:27What Are We Doing?
- 11:14Existing Workflow (+Steps) and Stakeholders
- 12:10Executable from Smartphones
- 13:13Contents of the Certificate Update Script (pem.sh)
- 14:31Contents of the Certificate Update Script
- 15:27Update Certificates During Build
- 18:55Leave Deliverables as CI Artifacts
- 22:06Automatically Synchronize Files to Build Machines
- 24:59Discontinuing Build Machines
- 30:07Comment on JIRA Tickets Upon Completion
- 31:00Toward an Ideal Workflow
- 36:53(Supplement) Automating Tool Updates
- 41:01Best Practices for Effective Automation
related talks
24mMobile development process automation
46mAutomatic Deployment of iOS and/or Android Apps
38mFrom Development to Production: Tips to Optimise Android App Deployments
20mScaling up a Super-App
31mDude, Where's My Build? Android CI/CD
40mAutomate The Small Things
47mMobile DevOps - Deliver great apps continuously
36mPutting together the best CI workflow for mobile apps