Hello guys, i have

--refresh-dependencies

parameter everytime at CI build job. But sometimes i get Cound not get HEAD from some pom file from maven central or Count not GET another lib. Is there possible, that the parameter causes this issues ? Maybe a few pipelines asks maven central very frequently and we get some anti DDOS blocks? Is there any way to add retry logic when gradle tries to fetch remote dependencies and failed could it try again from the same repository? If i remove this, is there possibility to break something on CI builds? Thank you for answering

If this is a corporate environment, you should anyway better have some local proxy and not constantly put load on Maven Central. See for example sonatype.com/blog/maven-central-and-the-tragedy-of-the-commons and blog.gradle.org/maven-central-mirror It could well be that MC blocks you if you query it too often. If you remove that parameter, nothing should break, because it will just reuse cached results if possible and if not because you use ephemeral agents without a shared dependency cache, then it will request the remote anyway.

Thnak you Bjorn 🙂

You're welcome, but it is Björn or Bjoern, not Bjorn. 🙂