How to Save Time with Ci and Build Time Reduction
summary
Shows concrete wins not vague promises: a 40k‑line Swift app with 38 CocoaPod deps and ~60 libraries takes 48 minutes to archive and test; switching to whole‑module compilation with no optimization drops CI to under 20 minutes, and replacing heavy libs with Carthage‑built frameworks shaves another ~10 minutes. Also automates workflows with Fastlane and danger, collects test‑coverage and timing in influxTV for dashboards, and uses debug‑time function‑body stats to find slow compiles.
AI-written summary · about
chapters (22)
- 0:00Start
- 4:55Sync dSYMs
- 5:24Release the App
- 6:36Check Labels
- 7:17Notify a New Build
- 7:49Dangerfile
- 9:30Post Code Coverage
- 10:13Visualize Code Coverage
- 10:46Other metrics
- 13:01Display build duration
- 13:50fastlane/report.xml
- 15:20Warn long function bodies
- 15:51Time function bodies
- 16:11xcactivitylog
- 17:18Test with Real Data
- 18:08Whole Module Optimization
- 18:26WMO without Optimization
- 20:08Carthage
- 21:11Xcode 9 New Build System
- 25:18dylib Loading Time
- 26:15Xcode 9 supports Swift Static Library
- 26:27Recap
related talks
59mCI Best Practices for iOS & macOS App Development
36mPutting together the best CI workflow for mobile apps
42mPorting iOS Apps to Bazel + Q&A
27mThe Need for Speed (in your CI/CD setup)
43mBuilding iOS Apps without Xcode
21mStreamlining Android app development and release processes
33mImprove the build times of your project
05mTips for Speeding Up Cargo Build in CI