A modern programming language that makes developers happier.

kotlinlang

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

```
./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])

ohh, interesting, that's great, let me check. Could you <@U7W5K3WJC> please tell me how long your builds are taking currently?

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 :disappointed:)

its ok, thanks :wink: Our builds are now quite fast