Hi. We have some builds runing on github CI and taking a lot of time in configuration. The problem, reading a build scan, seems to be that downloads from plugins.gradle.org are very slow. As an example, downloading https://plugins.gradle.org/m2/org/apache/apache/21/apache-21.pom took 26 seconds, at 641 bytes/second. Is this a known problem on the plugins servers, or is it some other network issue?
m
melix
03/08/2022, 2:44 PM
I've seen that too. The plugin portal is apparently under heavy load those days.
j
JB Nizet
03/08/2022, 2:45 PM
Happy to at least see weโre not the only ones suffering ๐
JB Nizet
03/08/2022, 2:47 PM
I think the answer is no, but given that we use a build cache on the CI, is there any way to configure gradle to fetch/store the plugins in/from the cache?
Thanks, I see. I was thinking of something more transparent, where the distributed build cache (which is already used to store and get task outputs) would also be used to store and get plugins. But my colleague is setting up the cache as explained there, thank you.
c
CristianGM
03/08/2022, 8:22 PM
I usually use the company Artifactory as cache for all the dependencies, but anyway it's not instant like the cache shown here (which I also use)
l
Louis Jacomet
03/08/2022, 8:27 PM
FYI the issue with the plugin portal is resolved and performance should be back to normal โฆ or even better ๐