This message was deleted.
# generals
Slackbot
03/08/2022, 2:41 PMThis message was deleted.
m
melix
03/08/2022, 2:44 PMI've seen that too. The plugin portal is apparently under heavy load those days.
j
JB Nizet
03/08/2022, 2:45 PMHappy to at least see we’re not the only ones suffering 😉
JB Nizet
03/08/2022, 2:47 PMI 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?
m
melix
03/08/2022, 2:51 PMif you use the official Gradle GH action, there's a dependency cache so it should work OOTB. Otherwise you'll have to do it yourself: https://docs.gradle.org/current/userguide/dependency_resolution.html#sub:shared-readonly-cache
j
JB Nizet
03/08/2022, 2:55 PMThanks, 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 PMI 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 PMFYI the issue with the plugin portal is resolved and performance should be back to normal … or even better 🙂
🎉 2