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/
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.
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.
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.
◦ 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
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.
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.
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.
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.
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.
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.
thedancercodes
rvirus0817
naoki_0531
goataka
yuj1osm
yamaguchitk333
yabakokobayashi
z63d
segavvy
matthewlujp
kongmingstrap
oniak3ibm
handy
stephaniewalter
kevinliebholz
dougneiner
reverentgeek
orderedlist
cromwellryan
tammielis
addyosmani
tenderlove
tammyeverts
shlominoach
bryan
