We have an Android project with around 90 library modules. During the configuration phase around 10k tasks are created and not executed. In total around 13k tasks are created and only 3k are executed. Mostly “testXYZ” tasks. This is under section “com.android.library”. For example:
assembleDebugAndroidTest, assembleDebugUnitTest, bundleDebugAndroidTestResources, bundleDebugUnitTestResources, etc.
We’re using “gradlew assembleBuildTypeFlavor” for this example to get Gradle build scan and the same is used for day to day deployment on devices.
Why are these tasks created and can they be filtered out for builds which don’t need them?
We’re using the newest Gradle (5.6.2), AGP (3.5.1) and so on.
PS: Can’t / shouldn’t be some of the above cached when there is no change to both gradle and kotlin / java / resource files?