https://kotlinlang.org logo
#android
Title
# android
c

czuckie

05/24/2019, 9:29 AM
gradle should be only executing tasks it needs to execute; the problem is when you want to have code coverage and you end up building with coverage enabled and then with coverage not enabled. I typically do compilation of instrumented classes upfront (quick verification the app compiles) and then run the tests. Then after tests have executed successfully, disable coverage and build all the product variants/flavours
Copy code
./gradlew -q compileDebugUnitTestKotlin
./gradlew -q assembleDebugAndroidTest
Will compile the unit tests, at which point, using Jenkins + pipelines, you could stash the workspace and unstash on multiple nodes to run your tests (jvm on one node, connected on another [ could even shard the connected tests by using annotations])
d

dave

05/24/2019, 10:01 AM
ohh, interesting, that's great, let me check. Could you @czuckie please tell me how long your builds are taking currently?
c

czuckie

05/24/2019, 12:19 PM
I could, but you won't have anything relative to compare it to, and I can't remember by how much it improved the build speeds (sorry 😞)
d

dave

07/23/2019, 11:11 AM
its ok, thanks 😉 Our builds are now quite fast