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

DevOps in the iOS world

48f07655aeed5ca639b37b05e52d4cb3?s=47 Piet Brauer
September 16, 2015

DevOps in the iOS world

Presented at NSSpain 2015


Piet Brauer

September 16, 2015

More Decks by Piet Brauer

Other Decks in Programming


  1. DevOps in the iOS World

  2. Who am I?

  3. Piet, Indie from Hamburg

  4. I make Git2Go

  5. Wait, What?

  6. #DevOps

  7. History » originated in 2008/2009 » months of release cycles

    to 10+ deploys a day » bring together devs and ops » ship faster
  8. Current iOS situation » Months of release cycles » Deploy

    from local Xcode » low automation
  9. The 3 ways

  10. No. 1: Systems Thinking

  11. No. 2: Amplifying Feedback

  12. No. 3: Culture of Continual Experimentation and Learning

  13. #iOSDevOps

  14. No. 1: Systems Thinking

  15. No. 2: Amplifying Feedback

  16. No. 3: Culture of Continual Experimentation and Learning

  17. #PracticaliOSDevOps

  18. No. 1: Systems Thinking

  19. The system Product Owner, UI Designer, UX Designer, Internal IT,

    Operations, iOS Feature Teams, iOS Platform Team, Apple
  20. None
  21. No. 2: Amplifying Feedback

  22. Shorten Feedback loop between ...

  23. You and Your Tests Get instant feedback if you broke

    something Travis CI, Cirlce CI, Jenkins, GitHub PullRequests, KIF, UIAutomation
  24. You and Apple Upload often, Release often, Automate everything possible

    Fastlane Tools, Shenzhen, TestFlight
  25. You and your customer Get feedback of your app, give

    feedback to customer, keep response time under 2 hours Supportkit, Slack, Mail
  26. You and your Designer Prototype, try new things, give them

    hints whats realistic Invision, AppCooker
  27. No. 3: Culture of Continual Experimentation and Learning

  28. Automate all the tasks, Introduce release cycles, get used to

    upload once a week, streamline your QA process, remove humans from every process
  29. Tools from 2009 / Conclusion 1.Automated infrastructure 2.Shared VCS 3.One

    step build & deploy 4.Feature Flags 5.Shared metrics 6.IRC and IM robots
  30. Culture from 2009 / Conclusion 1.Respect 2.Trust 3.Healthy attitude about

    failures 4.Avoid blame
  31. Further reading/watching » The Phoenix Project: A Novel about IT,

    DevOps, and Helping Your Business Win » Velocity 09: John Allspaw and Paul Hammond, "10+ Deploys Per Day"
  32. ! Thanks – @pietbrauer

  33. Q&A