Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Continuous Delivery For Mobile

Continuous Delivery For Mobile

This is a short, 10-minute talk that I gave at a Women Who Code Mobile Study Group meetup on how we continuously ship mobile releases monthly at PagerDuty.

Note: An older version of this talk was created and given by Clay Smith, one of our mobile engineers at the time, at TwilioConf 2015, so some slides here are shared with that.

Sweta (Vajjhala) Ackerman

October 26, 2015
Tweet

More Decks by Sweta (Vajjhala) Ackerman

Other Decks in Technology

Transcript

  1. 10/24/16 Basic “release to the masses” checklist CONTINUOUS DELIVERY FOR

    MOBILE WELCOME TO 2003… IN MARCH 2015 1. Write code. Try changes in the iOS or Android simulator or on a phone connected to your computer. 2. Run integration or unit tests (if they exist) locally. 3. Create an Android *.APK or iOS *.IPA (most likely in Xcode/Android Studio). 4. Distribute the build to testers using TestFlight, Crashlytics Beta, HockeyApp, iTunes Connect, Google Play (pick one). Test on physical devices. 5. Get feedback or crash reports (using Crashlytics), fix stuff. 6. Create a new release build to submit to the App Store or Play Store. 7. Hope it isn’t terrible. Too many button clicks and too manual.
  2. 10/24/16 Delivering Mobile Today: Travis CI Integration CONTINUOUS DELIVERY FOR

    MOBILE Result: build status appears in pull request on GitHub
  3. 10/24/16 All controlled by .travis.yml in source control CONTINUOUS DELIVERY

    FOR MOBILE http://www.objc.io/issue-6/travis-ci.html http://docs.travis-ci.com/user/languages/objective-c/
  4. 10/24/16 Delivering Mobile Today: More Bots! CONTINUOUS DELIVERY FOR MOBILE

    IN THE REAL WORLD IPA/APK for Testers Witty Build Status TEST SUITE RUNS ON ALL OF OUR PHYSICAL DEVICES!