Everything of CI/CD in Kyash Android Keisuke Kobayashi / kobakei CircleCI Japan Meetup: Mobile Edition 

About me • Keisuke Kobayashi • GitHub, Qiita: kobakei • Twitter: kobakei122 • Kyash, Inc • Using CircleCI for 3+ years 

Kyash Android 

Kyash Android • Full Kotlin • About 40 activities + Bottom Navigation • Architecture • MVVM + Layered architecture • Library • Rx, Dagger, Data binding, Retrofit & OkHttp, Picasso, Orma, Gson 

Continuous Integration 

Testing • Unit testing • UI testing 

Testing • Unit testing • UI testing 

Unit testing • Robolectric + Mockito • No emulator = fast • Focus on ViewModel and Model. 
 Activity and Fragment are not target. • Easy to inject mock objects by Dagger 2 • Run by git push on Circle CI 

mockito-kotlin • mockito extension for Kotlin • `when` problem • NPE on any • Easy to read & write 

@Test fun doAction_doesSomething(){ /* Given */ val mock = mock { on { getText() } doReturn "text" } val classUnderTest = ClassUnderTest(mock) /* When */ classUnderTest.doAction() /* Then */ verify(mock).doSomething(any()) } 

jacoco-android-gradle-plugin • Add gradle tasks to run unit test and code coverage • Need to exclude classes generated by kapt • Data binding, ORM, Parcelable, etc • No badge now • Codecov, Coveralls 

ktlint-gradle • Coding style checker and formatter for Kotlin • Default style is official style from kotlinlang.org • Not same as Android Studio default setting • Override: ktlint —apply-to-idea • Run style check on Circle CI 

cookpad/license-tools-plugin • Generate license page by gradle task • Check licenses on Circle CI • Avoid missing license 

Testing • Unit testing • UI testing 

UI testing • Espresso + UI automator • Use Espresso basically • Use UI automator to OS/other app UI (ex. permission dialog) • Don’t run on CI due to long exec time • Run before release to confirm important flows don’t degrade • ex. Sign up flow 

Mock in UI testing • MockWebServer of Retrofit • Unlike Mockito, JSON parse can be tested • Share MockWebServer object between Application class and test classes • Change API response at every test case 

Firebase Test Lab • Still experimental • Run UI testing on OS x device matrix • In parallel • Video recording in testing • 5 or 10 tests/day in free plan • Run before release manually? 

Continuous Delivery 

Crashlytics • Share the latest apk to team • master branch = debug build • Development endpoint • Debug screen with debot • Deploy at every git push (10~ times / day) • release/1.2.3 branch = beta build • Production endpoint • Deploy at code freeze 

Google Play • gradle-play-publisher • Gradle wrapper of Google Play Developer API • Need to set up Google API console • Can publish as alpha, beta and staging rollout • Triggered by GitHub Release (git tag) • However CircleCI 2.0 doesn't support tag… 

Workaround • Add CircleCI 1.0 deployment block deployment: fake_deploy_for_cci2: tag: /.*/ commands: - echo "make tags run in 2.0" 

Version name and code // App version def versionMajor = 1 def versionMinor = 11 def versionPatch = 2 // version code def vc = 0 if (System.getenv("CIRCLE_TAG") != null) { // tag = release build vc = versionMajor * 10000 + versionMinor * 100 + versionPatch } else if ("true" == System.getenv("CI")) { // no tag but CI = dev build vc = System.getenv("CIRCLE_BUILD_NUM") as Integer } else { // otherwise = local build vc = versionMajor * 10000 + versionMinor * 100 + versionPatch } 

CircleCI 

Like • Can start by free event if private repo • Many users • We can search YAML file on GitHub • Kind support • ex. Memory limit of my project has been increased before 

Dislike • OOM • Slow build • Official docs is still poor 

Dislike (CircleCI 2.0) • OOM Fixed? • Slow build Fixed • Official docs is still poor 

CircleCI 1.0 -> 2.0 Build time 60% down 

Breakdown (Total 5:30) 

Breakdown (Total 5:30) Unit testing Deploy 

I want… • Trigger by git tag • Firebase Test Lab on CircleCI 2.0 • Docs • There is only docs for CircleCI 1.0 • May need Docker image? 

Thanks!