iOS Release Pipeline

A public talk given at the Athens iOS Meetups group ( https://www.meetup.com/Athens-iOS-MeetUps/events/251197522/ ) in Athens on Tuesday, 12 June 2018.

A video of the of the talk is available at https://youtu.be/1Vbn7vd7EWY

Transcript

1. qnoid
2. qnoid iOS Release Pipeline A real world example of a distributed, in-house, release pipeline using Jenkins in an enterprise workspace.
3. qnoid generally speaking It was 5 years ago…
4. qnoid tools have changed
5. qnoid my memory is not that good
6. qnoid a bit of context and your imagination
7. qnoid this is the enterprise multiple teams, departments, stakeholders
8. qnoid multiple environments security reasons* (e.g. access to customer data)
9. qnoid feature branches one for each user story
10. qnoid develop on a branch
11. qnoid release on master
12. qnoid so, how did it look? an overview
13. qnoid development new feature
14. qnoid development new feature test summary test coverage monitor quality feedback loop
15. qnoid feedback loop must be sort
16. qnoid did we break the build? merges do that
17. qnoid monitor quality did we regress?
18. qnoid are tests failing? being hasty does that
19. qnoid so a day goes like this nine to five
20. qnoid development 9 a.m. 5 p.m.
21. qnoid hitting a beat making progress
22. qnoid development 1 a.m. 3 a.m. OTA download monitor progress demo features nightly notifications
23. qnoid demo day, every week monitor progress
24. qnoid development master end of sprint
25. qnoid development master end of sprint enable 3rd party libraries test summary integration tests security tests test 3rd party libraries release build
26. qnoid enable 3rd party libraries jailbreak, code obfuscation, anti tampering, etc.
27. qnoid integration tests against a staging server
28. qnoid security tests against a device
29. qnoid development master On success environment configuration environment builds
30. qnoid environment builds environment configuration (e.g. SSL)
31. qnoid master 1.0 On demand On demand production build (live proving, app store) archive build dSYM IPA
32. qnoid live proving and it’s off… for weeks
33. qnoid a big pile of scripts and ideas the technical details
34. qnoid time and effort
35. qnoid a script describing each build stage a configuration if you like
36. qnoid Jenkins setup too much involvement
37. qnoid development xcodebuild -scheme hello-world -configuration Debug clean build test
38. qnoid nightly xcodebuild -scheme hello-world -configuration Release -destination “generic/platform=iOS" archive -archivePath hello-world.xcarchive
39. qnoid nightly xcodebuild -exportArchive -archivePath hello-world.xcarchive -exportPath hello-world.ipa - exportOptionsPlist exportOptions.plist
40. qnoid environment builds resource substitution
41. qnoid Staging environment
42. qnoid ~jenkins/environments a list of environments per project
43. qnoid git ls-tree master \ --name-only “hello-world” a list of environments
44. qnoid git clone -b master \ ~jenkins/environments/$1 $1 = project name repository, e.g. “hello-world”
45. qnoid /development /staging /production
46. qnoid replace files just a copy
47. qnoid server.plist resource substitution
48. qnoid SSL Certificate resource substitution
49. qnoid build settings conditional compilation
50. qnoid build settings i.e. hello-world.xcconfig
51. qnoid compiler flags OTHER_SWIFT_FLAGS = $(inherited) -D SSL_PINNING
52. qnoid -D SSL_PINNING hello-world.xcconfig
53. qnoid #if SSL_PINNING conditional compilation
54. qnoid -xcconfig xcodebuild -scheme hello-world -configuration Debug clean build -xcconfig hello-world.xcconfig
55. qnoid ~jenkins/configurations support multiple releases per project
56. qnoid git clone -b hello-world-1.0 \ ~jenkins/configurations/hello-world support the hello-world-1.x branch
57. qnoid jenkins agents distributed building for free https://wiki.jenkins.io/display/JENKINS/Distributed+builds
58. qnoid use tags to distinguish xcode installations
59. qnoid a scheduler select the correct configuration given a project name and a branch
60. qnoid a distributed build system to scale
61. qnoid What support did it provide? with measurements or otherwise
62. qnoid 3 teams across 3 projects
63. qnoid automated builds/releases • 20 mins to deliver across all environments • 15 mins to deliver to production • Quality Gates (code coverage, tests run, security)
64. qnoid automated unit,integration tests • 2168 unit tests in 18 seconds • 33 integration tests in 2 mins 10 seconds
65. qnoid feedback loop mobile dev team QA team far long
66. qnoid feedback loop mobile dev team QA team close short
67. qnoid challenges keep them in mind
68. qnoid consistency across environments
69. qnoid “The Burden of Knowledge” Craig Russell https://medium.com/@trionkidnapper/the-burden-of-knowledge-52cc73508081
70. qnoid reproducing failures locally
71. qnoid a set of scripts obscure
72. qnoid disjointed user interface jobs rather than pipeline* * Jenkins Bue Ocean since then
73. qnoid not showing the full picture what settings where used? what environments?
74. qnoid Future work room for improvement
75. qnoid lots • record user scenarios to play back for look & feel and catch regressions • app should install and launch on every supported device/iOS version • performance testing i.e. memory/CPU usage and trend. • poor/no network connectivity scenarios. App shouldn't crash, should still be usable. • tested on different cellular network operators, proxies, network configurations.
76. qnoid lots • integration tests, spinning up “SIT” environments with a set of data • accessibility. App should be accessible for people with disabilities. • usability tests. • battery drain. • randomness. i.e user data, receiving a phone call while using the app, layout changes, localisation
77. qnoid Work of others to help you go further
78. qnoid “Continuous integration for iOS with Nix and Buildkite” Austin Louden | Pinterest engineer, Core Experience https://medium.com/@Pinterest_Engineering/continuous-integration-for-ios-with-nix-and-buildkite-ef5b36c5292d
79. qnoid www qnoid.com