Continuous Delivery for Android

Presented at Coding Serbia conference 2014

Abstract:
First Android phone was introduced in 2008 and now Android is dominating the market by a large margin. In these six years demand for Android development skills has increased significantly and is followed by demand of good tools to support fast and sustainable development of more complex applications.
Introduction of Gradle build system for Android application opened door for automating development processes. This includes automated builds, test runs and code quality inspections. Adding the automated application builds distribution to this list enables the closing of the continuous delivery cycle.
This talk will show how to integrate Continuous Delivery into your Android development using available open source tools.

Transcript

1. Continuous Delivery for Android
2. Speaker Nemanja Nedić Software developer @ Levi9 IT Services about.me/nemanjanedic
3. Agenda Continuous delivery concepts Gradle building blocks Configuring Jenkins build jobs Beta distribution using Crashlytics Demo
4. Continuous delivery concepts
5. Principles Every commit (push) can be a release candidate Automate (almost) everything Put everything in SCM Build only once Get feedback as early as possible Done means released
6. Build pipeline Automated manifestation of delivery process Establish automated quality gates Consists of build stages and steps Commit stage Automated acceptance test stage Manual test stage Release stage
7. Build steps for Android projects There is no easy way to automate publishing to Play Store What about automated acceptance tests? Build Run tests Code quality Upload artifacts Beta distribution
8. Gradle building blocks
9. Build Initial step of the pipeline Initiated on every commit (push) Compile and assemble clean assemble
10. Run tests Android tests require connected device or emulator Can be slow Create coverage report connectedCheck createDebugCoverageReport
11. Code quality Android Lint is your friend Use SonarQube for tracking the code quality Inspect code with SonarRunner Gradle plugin lint sonarRunner
12. Upload artifacts to Nexus Nexus is a good place to archive your builds Use Maven Gradle plugin uploadArchives
13. Upload APKs to Crashlytics Easy distribution of the builds to internal or external testers Also does crash reporting and analytics Setup using IDE plugin Use Crashlytics Gradle plugin crashlyticsUploadDistributionRelease
14. Jenkins build jobs
15. One build job per step
16. Gradle plugin Using wrapper is preferable Declare tasks to be run
17. Build name setter plugin Define more readable build names that can be consistent across the build jobs
18. Parameterized trigger plugin Define next build job in the pipeline Provide build number to subsequent jobs
19. Clone Workspace SCM plugin Archive all the files Archive only if the build is successful
20. Clone Workspace SCM plugin Reuse workspace from preceding build job
21. Build pipeline plugin
22. Beta distribution using Crashlytics
23. Dashboard
24. Client app
25. Demo
26. Questions?
27. Resources Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation http://www.amazon.com/Continuous-Delivery-Deployment- Automation-Addison-Wesley/dp/0321601912/ Building a Continuous Delivery Pipeline with Gradle and Jenkins http://www.infoq.com/presentations/cd-gradle-jenkins Sample app https://github.com/nemanjanedic/weatherly
28. Thank you!