CI at Shazam: a quest for shipping high-quality code

Video: https://twitter.com/londroid/status/976184582629244928
Twitter: @petz @edwardharks
Londroid @ Shazam

Transcript

1. CI @Shazam Edward Harker @edwardharks Francesco Pezzato @petz
2. What is CI/CD ?
3. Master (Cloud machine) Agent (Cloud machine) Agent (Cloud machine) Agent (Physical Machine) Our set up
4. Our set up
5. Our pipeline ./gradlew ./gradlew integrate
6. Environment checks
7. Static analysis
8. Unit Tests
9. UI Acceptance test
10. What is “Fast“? ~700 UI tests ~ 1h 50m on a single device (Nexus5)
11. Fork github.com/shazam/fork apply plugin: "com.shazam.fork" fork { testPackage = "com.shazam.android.tests" poolingStrategy = { .... } } ./gradlew fork ~ 10m across 15 devices
12. Release checks
13. All green?
14. Distribution
15. apply plugin: 'com.shazam.slackdistro' ./gradlew uploadDebugToSlack Anyone interested? Contact us, we are happy to open source it!
16. Flakiness
19. Performance Tests
21. Manual vs Automated Tests
25. GWEN github.com/shazam/gwen Blog post && open source Kotlin porting coming soooon!
28. Summary • If you don’t have any CI, start small • No need for Jenkins: there is plenty of online tools ◦ Appcenter, Bitrise, CircleCI, etc. • Physical devices cheaper than remote options in our case • But with local Jenkins: ◦ Fully configurable ◦ OSS and not owned by a single company ◦ Well adopted, plenty of plugins, large community ◦ More secure (no access from internet)
29. Thanks!