Failed to look up maven package in private artifactory

[MarekKromka]

How are you running Renovate?

Self-hosted Renovate

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 am trying to setup renovate on my project. It is using gradle and taking most of the dependencies from a mirrored maven repo from our own self-hosted artifactory. I am unable to set the hostRule so that renovate can look up dependencies in this particular artifactory.. All dependencies show e.g. Failed to look up maven package ... Dependency lookup unauthorized. Please add authentication with a hostRule for https://<our-server>/artifactory/maven2-all/org/slf4j/slf4j-simple/maven-metadata.xml

I tried a lots and lots of variation for a host rule specification currently I have ->

{ 
"matchHost": "https://<our-server>/artifactory/maven2-all/", "hostType": "maven", "token": "$BT_ARTIFACTORY_TOKEN" 
},

I tried curl with the $BT_ARTIFACTORY_TOKEN to see if that works.. it did returned 200... anyway the public repositories are available even without a token also returning 200 yet Renovate-bot seems to be unable to contact any...

I can see that the hostrule is added in the logs ->
DEBUG: Adding token authentication for https://<our-server>/artifactory/maven2-all/ (hostType=maven) to hostRules

I was suspecting that the runners which renovate-bot is using can't access this artifactory but same runners are used to build project without problem...

Any ideas ?

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[rarkins]

Please check the debug logs for all mentions of hostRules. The log message you captured just means that the hostRules is found in config and not that it's applied to requests

[MarekKromka]

There are no more occurrences of hostRules except for the config at the begining and already mentioned DEBUG: Adding token authentication for https://devops.bt.<ourOrgServer>.com/artifactory/maven2-all/ (hostType=maven) to hostRules

Before the actual request there is nothing regarding hostRules

So based on your answer I guess I am missing some configuration, hence the rule is not used for the HTTP request ?

[MarekKromka]

Found the culprit... Missing configuration for NO_PROXY env variable... Somehow it was causing problems for requests towards artifactory even thou it worked for curl without this setting...

So setting -> NO_PROXY: "$CODE_NO_PROXY,$CODE_NO_PROXY_JVM,devops.bt.<ourOrgServer>.com" works like a charm..

Make sure the delimiters are correct I tried it couple of days back with wrong delimiters, got no clue that it is wrong so I removed proxies from the list of suspects...