Slides for presentation kept in Devops Finland meetup 18.10.2016 It presents the journey Zalando Helsinki had towards the Continuous Delivery on iOS and bit on Android. https://www.meetup.com/devops-finland/events/234659906/

1. https://twitter.com/RamiRantala
https://www.linkedin.com/in/ramirantala

2. Continuous Delivery in mobile
Is it even possible?

4. 10 developers from different
teams
No testers - No QA department -
No iOS team

5. Gradle + Xcode plugin
..and Appium tests that were always broken

6. forks vs. branches

8. Continuous Integration
was quickly in place

9. Development
in feature
branch
Pull Request Merge
CI Build to
HockeyappReview Tag

10. RELEASE

11. Who will build RC?
Who will merge to master?
Who will upload it?
..AND WHY DO YOU RELEASE ON FRIDAY EVENING!?

12. It usually fired back on Monday.

13. Level 1

14. Development
in feature
branch
Pull Request
REVIEWER
Merges
CI Build to
HockeyappReview
Merge to master Tag Build
Upload to
Testflight
Tag
Submit

15. Fastlane

19. Fastlane works with Android
..and even with Gradle

20. Release Candidate
Automation

21. We automated RC build and upload from Master

22. How do you manage build numbers?
How do you know which CI is which RC?

23. Build numbers are kept in sync
CI 132 is from same code than RC 132 - and both are tagged
Version number 2.6.0 from plist
Buildnumber added to the end 2.6.0.132
Tags CI-2.6.0.132 and RC-2.6.0.132

24. Same build and source code twice to testflight?
2.6.0.13200
2.6.0.13201

25. Slack integration:
- build ci
- build rc latest
- build rc tag
- submit rc latest
- set version
- jenkins status
- have fun
- phantom

26. Level 2

27. Development
in feature
branch
Pull Request
DEVELOPER
Merges
CI Build to
HockeyappReview
Merge to master Build Tag
Upload to
Testflight
Tag
Submit

29. Daily Release Candidates

30. How do you merge master daily?
Who will do it daily?
Should you automate it?

31. We gave up master branch

32. Level 3

33. Development
in feature
branch
Pull Request
Merge to
develop
CI Build to
HockeyappReview
Build Tag
Upload to
Testflight
Tag
Send Release
Note and create
github release
Submit
Upload symbols
to Hockeyapp

34. How do you know what you have in build?
How do you know when to release?

36. Pull Request Checks

40. Slaves

41. Huge attitude changer

42. Level 4

43. Download
language
keys
Check if
they differ
Commit
Trigger
new CI
Separate track for language changes

44. Dev in
Feature
Branch
Pull
Request
Merge to
develop
CI Build to
Hockey
Review
and QA
Tag
Smoke tests Unit tests SwiftLint
PR Build to
Hockeyapp
Tests
CI automation for every commit

45. Build Tag
Upload to
Testflight
Send Release
Note
Submit if there is
no build in
process
Upload
symbols to
Hockeyapp
Create Mega
Report
Daily Release Automation (nightly)

46. Check if
release went
live
Get version
Mark version
as release in
github
Bump version
in plist
New Mega
Report
After release automation

47. What is difficult?
What have we learned?

48. Apple review time
Typically 2-3 days, sometimes even longer
You can’t have several versions in review at the same
time
Android does not have review time

49. Managerial mind
“Feature Freeze”
“Release Management”
“Release Plans”

50. Test automation and testing in general
Creating automated tests takes time
Running automated tests takes time
Only developers can create and develop tests fast
UI tests are constantly broken
Developers won’t create tests if you use technologies they are
unfamiliar with

51. What next?

52. Thank you.