Developing Gradle API
summary
A Gradle plugin is built in Groovy that automates Android build/versioning and ties builds to Jira and TeamCity: Jira status changes trigger version increments, git tags store semantic versions, TeamCity picks up tagged commits and Jira issues get the resulting version. The author extends an existing plugin to increment semantic versions, uses Gradle API hooks to handle init/config/execution phases and task wiring (finalizedBy, mustRunAfter), adds up‑to‑date checks and tests, and reports the workflow works and removes manual steps.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:21Plugin problem and motivation
- 13:39Why Gradle API
- 16:11Gradle plugin structure
- 21:11Task dependencies
- 26:32Mass task order execution
- 33:28Build lifecycle
- 34:10Additional tips
- 36:45Q&A
related talks
42mWrite your own Android Studio Plugin and automate everything
56mDeep Dive into the Android Gradle Plugin
39mKotlinify your Gradle
51mCreate Elegant Builds At Scale With Gradle
33mMake your Android Studio Plugin
32m5 ways to improve your Android build productivity
01h 03mKey Gradle Concepts And Practices
44mA Healthy Dose of Gradle
