Computer Says No — Static analysis and CI in a Kotlin world
summary
Concrete recipe for a CI that actually changes a repo: set up Gradle tasks to warm caches, run unit tests and assemble releases, wire them into a CircleCI pipeline that uses workspaces and parallel stages, and add Kotlin linters ktlint and static analyzers detekt plus Android Lint (optionally SpotBugs/SonarQube). Example runs on the open‑source Squanchy app, uses one free Linux executor or four for OSS, and delivers quicker feedback with zero budget.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:56Code Quality
- 2:48Testing
- 3:53Static Analysis
- 17:10Why adopting CI?
- 18:52CI services
- 21:46No ca$h? No worries.
- 22:40Anatomy of a CI
- 24:12The build queue
- 24:48A typical job
- 26:13A better job
- 27:23Pipelines
- 32:11Our example
- 33:39Getting started
- 37:55Configure CircleCI
- 43:28A CI run in detail
related talks
45mComputer Says No - Static Analysis and CI in a Kotlin Word
52mFrom Laptop Builds to Advanced CI
29mCompile, Deploy and Manage Your CI in Kotlin
46mDevelop your CI tools
41mKotlin Static Analysis with Android Lint
40mAutomate The Small Things
26mKotlinize your CI, from Gradle tuning to Kotlin Script
37mStatic Code Analysis For Kotlin