Continuous Delivery on Android

This talk covers the improvement of Hepsiburada.com Mobile team focusing on Android.
We mention tools we used while applying CD and trying to have a healthier codebase with best-practices applied.

Transcript

1. Continuous Delivery on Android Onur Kayabaşı @onurkayabasi Gökberk Ergün @faradaj
2. Hepsiburada.com • 500.000 product Monthly: • 15MM visitors • 26MM visits • 1,2MM transactions
3. Mobile Team’s Needs (Nov-2014) • Moving fast • Healthy codebase • Confidence • Reliability
4. Hepsiburada Mobile’s Improvement Android App Crash Counts (avg per 2-weeks) Source: Hepsiburada @ Fabric
5. Hepsiburada Mobile’s Improvement Android Play Store Ratings Source: Hepsiburada @ Play Store
6. HOW SHOULD WE WORK? *November 2014
7. ✓ Testable ✓ Continuosly Delivered (CD) ✓ Monitorable
8. Build Delivery Continuous Delivery Pipeline Integration Integration
9. Static Code Analysis Push Unit Tests Integration
10. Unit Tests
11. Static Code Analysis Push Unit Tests Integration FEST
12. Static Code Analysis Push Unit Tests Integration JaCoCo
14. Static Code Analysis Push Unit Tests Integration
15. Static Code Analysis Push Unit Tests Integration FEST JaCoCo
16. Build Integration Delivery Continuous Delivery Pipeline
17. Config Build Functional Tests Build Config ✓ Build Types ✓ Product Flavors
18. Build Functional Tests Build Config
19. Build Functional Tests Build Config
20. Functional Tests
21. Functional Tests
22. Functional Tests
23. Functional Tests
24. Build Functional Tests Build Config
25. Build Integration Delivery Continuous Delivery Pipeline
26. Integration Build Delivery Continuous Delivery Pipeline
27. Delivery • Beta user groups • Monitoring • Basic analytics • Crash reports
28. Integration Build Delivery Continuous Delivery Pipeline
29. Integration Build Delivery Continuous Delivery Pipeline
30. Continuous Delivery Best Practices • Make release version always available • Do not break the build (or fix immediately) • Keep the pipeline fast
31. Value of Continuous Delivery • Moving fast • More frequent and better releases HAPPY USERS
32. Short Term Goals ✓ Improvements on Pipeline • Distributing Calabash • Even faster builds (Buck, Gradle optimizations) • Continuous Inspection (Automatizing static code analysis) • Automatizing Memory Analysis ✓ Increasing coverage of Unit and Functional Tests ✓ Direct contribution to open source community
33. Onur Kayabaşı @onurkayabasi Gökberk Ergün @faradaj @faradaj