Gradle Scan Shows Slow Plugin on First Module

Asked Jan 22 '19 at 17:12

Active Feb 01 '19 at 15:48

Viewed 33 times

I've done a gradle build scan and noticed that plugins are being applied slowly to one module in the configuration phase. This module happens to be my first module. Is it known that the first module is slower for plugins or should I be investigating that module for slowdowns?

edited Feb 01 '19 at 15:48

Roberto Manfreda

2,345
3
25
39

asked Jan 22 '19 at 17:12

Zachary Sweigart

1,051
9
23

even applying these tricks? https://stackoverflow.com/questions/45327617/very-very-slow-gradle-build-on-android-studio – Roberto Manfreda Jan 22 '19 at 17:17
Yep all of those are added to my gradle.properties I wasn't sure if the issue was with the plugins themselves initializing since the first module takes 75% of the time – Zachary Sweigart Jan 22 '19 at 17:27
Try to invalidate the cache and restarting studio. I faced a problem like your and this worked for me. Double shift and type invalidate cache/restart :) You can make a try! – Roberto Manfreda Jan 23 '19 at 09:46
These are scans from a command line build, but I'll give it a try – Zachary Sweigart Jan 24 '19 at 18:54
Show us your `build.gradle` files please. – Jared Burrows Jan 25 '19 at 06:50

Gradle Scan Shows Slow Plugin on First Module

0 Answers0