Continuous Delivery for Native Apps
summary
Argues that continuous delivery for native apps means always having a release‑ready binary (not automatic App Store deploys) and shows a working pipeline: Jenkins auto‑creates branch jobs from Git feature branches, builds signed binaries, pushes per‑branch installs to HockeyApp, and runs Calabash/Cucumber UI tests. Uses a backdoor API to speed setup, a rerun formatter to re‑run flaky scenarios, nine cloned test environments, and a ~1h30 full iPad test suite; outcome is stable master, fast hourly/nightly feedback, occasional simulator flakiness but overall more frequent safe releases.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:00The Apps
- 1:25Tools
- 2:03Branching
- 5:27How we do it
- 6:05Jenkins jobs
- 8:40Prerequisites
- 9:43Optional hooks
- 10:38Tests
- 13:34Cucumber
- 14:47Cucumber walkthrough
- 16:55Crossplatform
- 18:33Page Objects
- 20:15Timing Issues
- 22:06Testing Issues
- 22:58Cucumber formatter
- 24:38Test suites
- 32:51Test Automation
- 35:06Trust
- 37:34Agility
- 39:02Prepare
- 41:13Embrace failures
related talks
47mMobile DevOps - Deliver great apps continuously
41mImplementing Continuous Delivery with IOS
26mContinuous Everything in Mobile
43mSecret Sauce of Cross-platform Mobile App Continuous Delivery
15mWeb-like Release Agility for Native Apps
40mContinuous Delivery for Mobile
44mContinuous Integration with Xamarin Apps
24mWhy, What, and How of Continuous Delivery