intermediate · self-paced
Gradle Enterprise Builds
Author multi-module builds, share convention plugins, and shorten feedback loops responsibly.
4 weeks · 5h/week
JPY 54,000
Informational rate—final fees appear on your enrollment agreement.
Request information Money-back policyProgram narrative
Gradle is treated as code: convention plugins, version catalogs, and configuration cache pitfalls. You will migrate a sample monolith from fragile Groovy scripts to Kotlin DSL with documented trade-offs, and interpret build scans to justify caching investments to managers.
What ships in the box
- Version catalog patterns with semantic versioning discussion
- Composite builds lab linking libraries locally
- Configuration cache troubleshooting tree
- Gradle Enterprise scan reading workshop (sample data)
- Publishing artifacts to private repositories mock
- Checklist for plugin upgrades across teams
- Pair review on your own build file (redacted)
Outcomes you can describe
- Propose a caching change backed by scan evidence
- Extract a convention plugin your teammates can reuse
- Explain DSL choices to a Groovy-friendly team without drama
Lead mentor
Jonas Weber
Backend mentor; built payment adapters across EU and JP regions.
Cohort questions
We draw comparisons, but deliverables are Gradle-only.
Not required; we use anonymized scans and open-source features.
Bazel or Pants migrations, Android Gradle Plugin deep dives, and custom IDE plugin authoring.
Experience notes
Convention plugin extraction finally stopped our copy-paste scripts across eight services.