[Feature] Summary count tasks about dexcount-gradle-plugin

[benjamin-bader]

Right now you could do single-flavor counts by doing ./gradlew assembleFlavor1Release, which would build and dex just that one flavor - I'm actually in your same boat (with NDK plus multiple flavors), so that's what I do.

The way it currently works, the count task's name and existence is predicated entirely on what variants are being assembled. Can you just update the counts directly from the build job?

[vanniktech]

I figured out yesterday that those summary tasks don't really help. I had the assumption that the count tasks depend on something other than the actual APK(s). Since the check Jenkins Job never actually builds APKs those summary tasks are useless.

I guess your solution of using ./gradlew assembleFlavor1Release is best. Maybe I'll just do another Jenkins Build that only plots the dexcounts and does nothing else as that would not take that long since Unit Tests and all of the static analyze tools won't run. Also an incremental build for that Jenkins task would be an option in order to speed up the build process.

[benjamin-bader]

As it doesn't seem that there is anything to do, I'm closing this issue.