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/
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
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?
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
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
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