The Art of Mobile DevOps : Android Improving your team’s Android Build Performance & Productivity. @thedancercodes ~ Roger Taracha ~ 

About Me ● Software Engineer. ● Python, JS, Android ● Dance Choreographer. ● Traveling. ● Community Development. ● DIY Hobbyist. ● Learning Facilitator/ Technical Team Lead - Andela 

We are hiring! 

What is DevOps? DevOps is derived from two words: development and operations. As the word suggests, it is a set of practices in a process while developing software and managing operations tasks. DevOps is not just a set of practices, but also a way of working in the software development industry; it’s a cultural change in the way development and operations work together. https://devops.com/metrics-devops/ 

Why DevOps? ● Devops enables quick solutions in the case of a technical glitch. ● Contributes to team health, individual satisfaction. ● Time efficiency & Management. ● Devops gives us the facility & flexibility to invent & focus on actual business needs instead of taking hours/ weeks/ months of operational tasks. ● To deploy often, you can’t break what’s already there, you have to complement it. 

Focus Areas It is impossible to speak about DevOps without mentioning the following areas: ● Continuous Integration. ● Continuous Delivery/Deployment. 

What is CI? ● Continuous Integration is a development practice that requires developers to integrate code into a shared repository several times a day. ● Each checkin is then verified by an automated build, allowing teams to detect problems early. 

Why CI? ● Deliver faster & higher quality. ● Your product is always ready to deploy. ● Capture institutional knowledge in tests. ● Automation hugely improves productivity. ● Multiply your impact 

Delivery vs Deployment ● Continuous Delivery => Software can be deployed to customers at any time with the "push of a button" (i.e. by running a deployment script). ● Continuous Deployment => Software is automatically deployed to customers once it passes through the continuous integration system. 

Case Study Converge Android - An Internal Product We needed a way to ensure that we can deploy the product quickly and have a working product at any point in our development lifecycle. 

Team Structure & Tools ● Current Team Structure: ○ Backend ○ Frontend ○ Mobile ○ DevOps ● Getting the team balance at the beginning was a bit of a challenge. ● Lots of communication and stakeholder management was needed to make things work. Tools: ● Github Enterprise ● Code Climate ● Circle CI ● Static code analysis tools ○ PMD, Checkstyle, Findbugs, Android Lint ● Gradle - Build Scans ● Flank - a massively parallel Android and iOS test runner for Firebase Test Lab. ● Fastlane 

CI Pipeline 

Code Climate An open, extensible platform for automated code review for test coverage, complexity, duplication, security, style, and more. 

Static Analysis Tools ● Improving Code Quality & Syntax of your Android Code ● Poor code quality and technical debt inevitably lead to developer productivity losses, missed deadlines, and a higher bug rate. ● Complements code reviews through peers. ● Static code analysis tools help you enforce coding standards and uncover bad coding practices and potential bugs. ● Gradle offers a wide range of standard plugins for you to pick and choose from. ● NOTE: We use pre-commit hooks with these tools. 

Gradle ● Gradle, an advanced build toolkit, to automate and manage the build process, while allowing you to define flexible custom build configurations. ● Gradle and the Android plugin run independent of Android Studio. This means that you can build your Android apps from within Android Studio, the command line on your machine, or on machines where Android Studio is not installed (such as continuous integration servers). ● NOTE: The output of the build is the same whether you are building a project from the command line, on a remote machine, or using Android Studio. 

No content

No content

Output: APK Develop = Sends APK to Slack Staging and Master?! 

Enter Continuous Delivery/ Deployment 

Delivery vs Deployment ● Continuous Delivery => Software can be deployed to customers at any time with the "push of a button" (i.e. by running a deployment script). ● Continuous Deployment => Software is automatically deployed to customers once it passes through the continuous integration system. 

No content

No content

NOTE: We use Staging to push to Alpha/ Beta Channel and Master to push to Production. Might not be ideal but works for us. :) 

Tips to Reduce your Build Times... ● General Optimizations: ○ Using up-to-date library versions ● Build Scans: ○ A persistent record of what happened in a build. ○ A great debugging and collaboration tool. ● Modularization: ○ Process of taking a big single module app and splitting it into multiple modules. 

General Optimizations Before getting into the specifics, let’s make sure you have the basics down: ● Latest Gradle version ● Latest AGP version ● Latest Kotlin version ● Don’t disable the Gradle Daemon ● Make sure org.gradle.caching =true in your gradle.properties file ● If possible, enable org.gradle.parallel too, especially if you have multiple modules. 

Gradle: Build Scans ● A build scan is a shareable and centralized record of a build that provides insights into what happened and why. ● In your terminal, run this command: $ ./gradlew build --scan 

Modularization ● Process of taking a big single module app and splitting it into multiple modules. ● Extracting rarely-changed code reduces build time. ● Decoupled code => Faster incremental compilation ● Intermodule dependencies increase build time. ○ If you have spaghetti code, where everyone is referencing everyone, incremental compilation can’t help that much. 

“There is no silver bullet when it comes to optimizing your build performance, you have to do the work & find what works for you.” Boris Fraber (Google) 

Reference Material: ● Gradle Performance Guide: ○ https://guides.gradle.org/performance/ ● Android Performance Guide: ○ https://developer.android.com/studio/build/optimize-your-build ● Plugin Development Guide: ○ https://guides.gradle.org/implementing-gradle-plugins/ ● Structuring build logic guide: ○ https://docs.gradle.org/current/userguide/organizing_gradle_projects.html ● DIY Gradle build optimization ○ https://proandroiddev.com/gradle-perf-9c11b640f329 

“The result of an optimized & reliable BUILD PERFORMANCE is FASTER feedback cycles and IMPROVED efficiency of your team.” 

Thank you @thedancercodes TheDancerCodes TheDancerCodes