Consider tweaking the build to only run tests for affected files.

[anuraaga]

I use this technique of reading the git diff to run tests in monorepos

https://github.com/curioswitch/curiostack/blob/master/tools/gradle-plugins/gradle-curiostack-plugin/src/main/java/org/curioswitch/gradle/plugins/ci/CurioGenericCiPlugin.java

This agent is even more of a monorepo than than many I've experienced :) I generally like them but think this sort of "only build affected targets" technique is what makes or breaks the experience.

[iNikem]

I will repeat myself from #526 :)

"I would really love to try #490 first. It may, in theory, reduce build times significantly for us."

[trask]

@anuraaga is this resolved by all of the gradle build cache work?

[anuraaga]

@iNikem Did we ever make the build cache public for users' builds? If not, I think this could still be a reasonable alternative. FWIW, I notice ./gradlew check to take forever almost all the time :P

[iNikem]

We still have an unresolved issue that remote build cache does not work for developers machine.

[trask]

Closing, can revisit later if anyone has renewed interest.