Mobile CI/CD in 2k19

In order to understand how to build your CI/CD pipeline, you need to know what a base technology you use? React-Native, Swift iOS app, Flutter app? Where do you checkout your sources? Where do you want to deploy it? What side capabilities your pipeline should have?

Transcript

1. MOBILE CI/CD IN 2K19 1
2. VLADIMIR IVANOV EPAM SYSTEMS MOBIUS CONF 2
7. CD 7
11. CI 11
12. WHAT DO WE LOVE? 12
13. WRITE CODE! 13
14. WHAT WE DISLIKE? 14
15. EVERYTHING ELSE! 15
16. BUT STILL 16
17. BUT STILL > Code Quality 16
18. BUT STILL > Code Quality > Customer Transparency 16
19. BUT STILL > Code Quality > Customer Transparency > Developer Satisfaction 16
20. IT IS IMPORTANT! 17
21. WHAT SHOULD BE DONE 18
23. > run Lint/Static Analysis on the Code 19
24. > run Lint/Static Analysis on the Code > run Unit Tests 19
25. > run Lint/Static Analysis on the Code > run Unit Tests > maintain Build Numbers 19
26. > run Lint/Static Analysis on the Code > run Unit Tests > maintain Build Numbers > build the App from Code 19
27. > run Lint/Static Analysis on the Code > run Unit Tests > maintain Build Numbers > build the App from Code > deploy the App 19
28. > run Lint/Static Analysis on the Code > run Unit Tests > maintain Build Numbers > build the App from Code > deploy the App > notify about status 19
29. > run Lint/Static Analysis on the Code > run Unit Tests > maintain Build Numbers > build the App from Code > deploy the App > notify about status > provide Logs, Artifacts & Build Reports 19
30. > run Lint/Static Analysis on the Code > run Unit Tests > maintain Build Numbers > build the App from Code > deploy the App > notify about status > provide Logs, Artifacts & Build Reports > and actually many more 19
33. SOURCE CODE 22
34. SOURCE CODE 23
35. SOURCE CODE > Checkout from where? 23
36. SOURCE CODE > Checkout from where? > How to build? 23
37. SOURCE CODE > Checkout from where? > How to build? > How to test? 23
38. CHECKOUT 24
39. GIT HOSTINGS 25
40. GIT HOSTINGS > Saas: Github, Bitbucket, Gitlab, Azure DevOps, AWS CodeCommit 25
41. GIT HOSTINGS > Saas: Github, Bitbucket, Gitlab, Azure DevOps, AWS CodeCommit > On-premise: Github Enterprise, Gitlab, Bitbucket Server 25
42. GIT HOSTINGS > Saas: Github, Bitbucket, Gitlab, Azure DevOps, AWS CodeCommit > On-premise: Github Enterprise, Gitlab, Bitbucket Server > Ad-Hoc 25
44. > Checkout different branches 26
45. > Checkout different branches > Trigger different builds on VCS commit/pull request 26
46. > Checkout different branches > Trigger different builds on VCS commit/pull request > Report build status to a VCS back 26
47. WHY IT IS IMPORTANT? 27
50. > Eslint 29
51. > Eslint > swiftlint 29
52. > Eslint > swiftlint > Java/Kotlin linters 29
53. > Eslint > swiftlint > Java/Kotlin linters > FindBugs 29
54. PRECOMMIT HOOKS 30
56. VALIDATE CODE BASE ON PULL REQUEST/PUSH 32
57. BUILD 33
60. BUILD SHOULD BE 36
61. BUILD SHOULD BE > Reliable (isolated&clean) 36
62. BUILD SHOULD BE > Reliable (isolated&clean) > Fast (on performant machines) 36
63. BUILD SHOULD BE > Reliable (isolated&clean) > Fast (on performant machines) > Locally reproducible (to debug) 36
64. BUILD SHOULD BE > Reliable (isolated&clean) > Fast (on performant machines) > Locally reproducible (to debug) > Customizable (for envs or other params) 36
65. BUILD SHOULD BE > Reliable (isolated&clean) > Fast (on performant machines) > Locally reproducible (to debug) > Customizable (for envs or other params) > Secure (only allowed persons to create/edit/run builds) 36
66. SIGN 37
67. SIGN > Secure storage for provisioning profile/signing certificate/keystore 37
68. SIGN > Secure storage for provisioning profile/signing certificate/keystore > Secure storage for password 37
69. SIGN > Secure storage for provisioning profile/signing certificate/keystore > Secure storage for password > Account storage for pushing to Google Play/Test flight/3rd party services 37
70. DEPLOY 38
73. DEPLOY 41
74. DEPLOY > Connect to distribution services 41
75. DEPLOY > Connect to distribution services > Manage upload secrets 41
76. TESTING 42
78. TESTING 44
79. TESTING > Unit/Module tests 44
80. TESTING > Unit/Module tests > e2e tests 44
81. ISSUES E2E TESTS 45
83. ISSUES E2E TESTS 47
84. ISSUES E2E TESTS > Takes a lot of time 47
85. ISSUES E2E TESTS > Takes a lot of time > Requires devices 47
86. MISCELLANEOUS 48
87. MISCELLANEOUS > Configuration as code 48
88. MISCELLANEOUS > Configuration as code > Debug locally 48
89. MISCELLANEOUS > Configuration as code > Debug locally > Centralized user management(SSO) 48
90. MISCELLANEOUS > Configuration as code > Debug locally > Centralized user management(SSO) > Auto-configuration 48
91. MISCELLANEOUS > Configuration as code > Debug locally > Centralized user management(SSO) > Auto-configuration > Extensions 48
92. YOUR CI/CD PIPELINE SHOULD SUPPORT IT ALL! 49
93. APPROACHES 50
94. APPROACHES 51
95. APPROACHES > Install Jenkins/TeamCity/Whatever else 51
96. APPROACHES > Install Jenkins/TeamCity/Whatever else > Spawn a Jenkins VM/Container in a Cloud 51
97. APPROACHES > Install Jenkins/TeamCity/Whatever else > Spawn a Jenkins VM/Container in a Cloud > Use Saas 51
98. LOCAL JENKINS 52
99. LOCAL JENKINS > Free 52
100. LOCAL JENKINS > Free > Great flexibility 52
101. LOCAL JENKINS > Free > Great flexibility > Agents system 52
102. LOCAL JENKINS > Free > Great flexibility > Agents system > Decent plugin system 52
103. LOCAL JENKINS > Free > Great flexibility > Agents system > Decent plugin system > But no containerization out-of-the- box 52
104. LOCAL JENKINS > Free > Great flexibility > Agents system > Decent plugin system > But no containerization out-of-the- box > All support burden is on your shoulders 52
105. WHEN 53
106. WHEN > For education purposes and student projects 53
107. WHEN > For education purposes and student projects > For companies which already use Jenkins 53
108. WHEN > For education purposes and student projects > For companies which already use Jenkins > For security paranoids(debatable) 53
109. JENKINS IN CLOUD 54
110. JENKINS IN CLOUD > Solve the containirazion issue 54
111. JENKINS IN CLOUD > Solve the containirazion issue > Support burden is partially decreased 54
112. 3RD PARTY SERVICES 55
113. 3RD PARTY SERVICES 56
114. 3RD PARTY SERVICES > Circle CI 56
115. 3RD PARTY SERVICES > Circle CI > GitLab CI 56
116. 3RD PARTY SERVICES > Circle CI > GitLab CI > Nevercode 56
117. 3RD PARTY SERVICES > Circle CI > GitLab CI > Nevercode > App Center 56
118. 3RD PARTY SERVICES > Circle CI > GitLab CI > Nevercode > App Center > Bitrise 56
119. 3RD PARTY SERVICES > Circle CI > GitLab CI > Nevercode > App Center > Bitrise 57
120. APP CENTER 58
121. APP CENTER - AZURE DEVOPS 59
122. APP CENTER - AZURE DEVOPS > Part of the integrated environment(former TFS) 59
123. APP CENTER - AZURE DEVOPS > Part of the integrated environment(former TFS) > Distribution destinations - GP, TestFlight, Internal 59
124. APP CENTER - AZURE DEVOPS > Part of the integrated environment(former TFS) > Distribution destinations - GP, TestFlight, Internal > Bitbucket, Github, VSTS 59
125. APP CENTER - AZURE DEVOPS > Part of the integrated environment(former TFS) > Distribution destinations - GP, TestFlight, Internal > Bitbucket, Github, VSTS > Configuration as Code 59
126. APP CENTER - AZURE DEVOPS > Part of the integrated environment(former TFS) > Distribution destinations - GP, TestFlight, Internal > Bitbucket, Github, VSTS > Configuration as Code > Mobile Apps as first class citizens 59
127. APP CENTER - AZURE DEVOPS > Part of the integrated environment(former TFS) > Distribution destinations - GP, TestFlight, Internal > Bitbucket, Github, VSTS > Configuration as Code > Mobile Apps as first class citizens > Cloud based 59
128. APP CENTER - AZURE DEVOPS > Part of the integrated environment(former TFS) > Distribution destinations - GP, TestFlight, Internal > Bitbucket, Github, VSTS > Configuration as Code > Mobile Apps as first class citizens > Cloud based > Webhooks 59
129. APP CENTER - AZURE DEVOPS 60
130. APP CENTER - AZURE DEVOPS > Support for ad-hoc git servers 60
131. APP CENTER - AZURE DEVOPS > Support for ad-hoc git servers > Support CI job triggers on push to Any branch 60
132. APP CENTER - AZURE DEVOPS > Support for ad-hoc git servers > Support CI job triggers on push to Any branch > SonarQube Support - 60
133. APP CENTER - AZURE DEVOPS > Support for ad-hoc git servers > Support CI job triggers on push to Any branch > SonarQube Support - > Local debug - 60
134. APP CENTER - WHEN 61
135. APP CENTER - WHEN > You already have Azure DevOps/Azure subscription 61
136. APP CENTER - WHEN > You already have Azure DevOps/Azure subscription > You're hosted in Bitbucket/Github 61
137. APP CENTER - WHEN > You already have Azure DevOps/Azure subscription > You're hosted in Bitbucket/Github > You only want apps distribution solution 61
139. NEVERCODE 63
140. NEVERCODE > Mobile Centric CI/CD 63
141. NEVERCODE > Mobile Centric CI/CD > Distribution destinations - App Store Connect, Google Play, HockeyApp, Crashlytics, TestFairy 63
142. NEVERCODE > Mobile Centric CI/CD > Distribution destinations - App Store Connect, Google Play, HockeyApp, Crashlytics, TestFairy > Bitbucket, GitHub or GitLab 63
143. NEVERCODE > Mobile Centric CI/CD > Distribution destinations - App Store Connect, Google Play, HockeyApp, Crashlytics, TestFairy > Bitbucket, GitHub or GitLab > Cloud based 63
144. NEVERCODE > Mobile Centric CI/CD > Distribution destinations - App Store Connect, Google Play, HockeyApp, Crashlytics, TestFairy > Bitbucket, GitHub or GitLab > Cloud based > Mobile Apps as first class citizens 63
145. NEVERCODE > Mobile Centric CI/CD > Distribution destinations - App Store Connect, Google Play, HockeyApp, Crashlytics, TestFairy > Bitbucket, GitHub or GitLab > Cloud based > Mobile Apps as first class citizens > Webhooks 63
146. NEVERCODE 64
147. NEVERCODE > Configuration as Code 64
148. NEVERCODE > Configuration as Code > Pricy 64
149. NEVERCODE - WHEN 65
150. NEVERCODE - WHEN > Flutter apps 65
151. BITRISE 66
152. BITRISE > Mobile Centric CI/CD 66
153. BITRISE > Mobile Centric CI/CD > Distribution destinations - GP, TestFlight, TestFairy, App Center, Whatever 66
154. BITRISE > Mobile Centric CI/CD > Distribution destinations - GP, TestFlight, TestFairy, App Center, Whatever > Bitbucket, Github, Custom 66
155. BITRISE > Mobile Centric CI/CD > Distribution destinations - GP, TestFlight, TestFairy, App Center, Whatever > Bitbucket, Github, Custom > Configuration as Code 66
156. BITRISE > Mobile Centric CI/CD > Distribution destinations - GP, TestFlight, TestFairy, App Center, Whatever > Bitbucket, Github, Custom > Configuration as Code > Mobile Apps as first class citizens 66
157. BITRISE > Mobile Centric CI/CD > Distribution destinations - GP, TestFlight, TestFairy, App Center, Whatever > Bitbucket, Github, Custom > Configuration as Code > Mobile Apps as first class citizens > Cloud based 66
158. BITRISE > Mobile Centric CI/CD > Distribution destinations - GP, TestFlight, TestFairy, App Center, Whatever > Bitbucket, Github, Custom > Configuration as Code > Mobile Apps as first class citizens > Cloud based > Webhooks 66
159. BITRISE 67
160. BITRISE > Support for ad-hoc git servers 67
161. BITRISE > Support for ad-hoc git servers > Support CI job triggers on push to Any branch 67
162. BITRISE > Support for ad-hoc git servers > Support CI job triggers on push to Any branch > SonarQube Support with a community extension 67
163. BITRISE > Support for ad-hoc git servers > Support CI job triggers on push to Any branch > SonarQube Support with a community extension > Local debug - 67
164. BITRISE > Support for ad-hoc git servers > Support CI job triggers on push to Any branch > SonarQube Support with a community extension > Local debug - > Open source 67
166. BITRISE 69
167. BITRISE > Rather slow 69
168. BITRISE > Rather slow > No Flutter support(yet) 69
169. CONCLUSIONS App Center Nevercode Bitrise Simplicity ✅ Flutter ✅ Flexible ✅ Device Cloud ✅ Build cache ✅ Build cache ✅ Crash Reporting ✅ No Xamarin ❌ Different inf. stacks ✅ Difficult customization ❌ No conf as service ❌ Open Source ✅ Funny jokes Slow ❌ 70
171. LINKS 72
172. LINKS > https://twitter.com/vvsevolodovich ! 72
173. LINKS > https://twitter.com/vvsevolodovich ! > https://medium.com/@dzigorium " 72
174. LINKS > https://twitter.com/vvsevolodovich ! > https://medium.com/@dzigorium " > https://mobiusconf.com/ 72
175. LINKS > https://twitter.com/vvsevolodovich ! > https://medium.com/@dzigorium " > https://mobiusconf.com/ > Vladimir_Ivanov4@epam.com 72