Maven dependency resolution performance #27768
Replies: 2 comments 7 replies
-
Ok so I did a bit of further research and found out the following: 1.There is an environment variable called I enabled it, now my Renvoate needs 30s for dependency resolution instead of 90s and sends 100 requests to Maven Central instead of ~3k. 2.I think that you should get completely rid of the This PR addresses #4471 and renovatebot/config-help#529 which are both cases where people are using a misconfigured Maven Repository where the Artifact Level IMHO the solution here is to fix the broken
|
Beta Was this translation helpful? Give feedback.
-
Update Nov 2024:
|
Beta Was this translation helpful? Give feedback.
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitLab
Please tell us more about your question or problem
I likely found 2 improvements regarding Maven dependency resolution for Maven Central (
https://repo1.maven.org/maven2/
).I noticed these problems after further inspecting logs due to #27621 / #27759 and finding out that a small Maven project with ~30 dependencies sent around 3k request to maven central:
index.html
to lookup Maven releases (e.g. https://repo.maven.apache.org/maven2/org/testcontainers/testcontainers-bom/index.html), however Maven Central hosts no such file and the requests always fail.maven-metadata.xml
file (that is used for enumerating all dependency versions).I recommend the following changes for
https://repo1.maven.org/maven2/
and they likely should be ship by default with renovate:index.html
for lookupLogs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions