Diagnose build issues, benchmark build performance, and analyze build changes by benchmarking Gradle build performance using gradler-profiler.
Better understand Gradle in your Android builds, how it relates to the Android Gradle Plugin, and finally how to profile and optimize your Android Gradle build.
How can you make Gradle build scan URLs more visible in your GitHub Actions workflows?
A while back, I wrote about simplifying our app distribution process using Beta by Crashlytics.
Since that time, I had been thinking (and receiving questions) about how to handle multiple buildTypes and productFlavors more gracefully. When I originally described our approach we only needed to worry about a single build target. After a while, we added a second productFlavor and the fastest solution was to simply copy our custom gradle tasks and make new versions for the new build target.
That solution got us up and running quickly, but it always bothered me that we now had a sizable chunk of duplicate code in our gradle file. When it came time to add yet another product flavor, the time had come to think about a better solution
Thankfully, it was pretty easy to leverage the power of gradle to create custom distribution tasks for each buildType/productFlavor combination without having to manually duplicate any code.
I wrote a follow up to this post in which I describe a more straightforward version the approach detailed here.