Automate All The Things!
summary
Automated CI uses GitHub Actions (also shown on CircleCI) to run Gradle builds, ktlint pre-push hook copied from repo scripts so formatting fails locally not on CI, scheduled dependency checks at 08:00 that list outdated libraries, and Crashlytics distribution on develop plus Play Store publish on merge to master via Gradle Play Publisher. Danger posts danger inline lint comments and APK size warnings, turning build logs into actionable PR comments and catching size regressions.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:16Why Do We Want To Automate Things
- 4:51General Automated Build
- 6:33An Automated Build
- 8:47Pull Requests and Issues
- 11:18Status Checks before Merging
- 12:15Validating Code Quality
- 13:29Katy Lint
- 15:39Reformatting Code Using the Ide
- 16:32Optimize Imports on-the-Fly
- 17:32Android Studio
- 18:27Get Hooks
- 22:06Review the Code
- 24:39Github Pull Request Templates
- 30:14Conditional Logic
- 33:27Lint Checks
related talks
40mAutomate The Small Things
42mFocus on What Matters by Automating the Small Things
48mBuilding an Android CI Pipeline With GitHub Actions
18mAutomating All the Code & Testing Things with GitHub Actions
28mAutomate Everything
29mA brief guide to setting up CI for Android with GitHub Actions
30mAutomate all the things with CI/CD in GitHub Actions
08mAutomated Checks Before Publishing Open Source, a Few Years La...