We basically have a white label app for Android that produces about 40 apps. The build as you can guess is terribly slow and on top of that our modules are poorly organized. But for right now is there a lazy and quick way to fix some of the build time (So when we do the builds on our CI all of those modules are done over and over again): Modules: app - very small app independent home - has all the custom resources for each of the forty+ apps and a majority of the code frescoExt - app independent a fresco extension Networking - app independent player - app independent Is there a way to make all the modules that generate a lib/aar to do it once and the home module just references the lib/aar that those other modules produce? Introducing a repo server is probably not going to be possible, but we do have a github account if that can be used in some way.

You should probably look into using a remote build cache. So then the CI server that first produces a cacheable task output it can put them there and further executions for the same inputs can then reuse that cache entry.

Adding

--scan

to a gradle builds uploads some stats to gradle for viewing. They often come with a handful of tips to improve build performance.

Also: https://docs.gradle.org/current/userguide/performance.html

Parallel build can help if it's not enabled already. Just add these two lines to your project's

gradle.properties

file to enable local caching and parallel execution:

org.gradle.parallel=true
org.gradle.caching=true

Aaand if you need further tipps, have a look at the channel subject first to find a more appropriate place to ask, as your question actually is off-topic here. 😉