Unable to authenticate to private Google Artifact Registry for gradle packages #33084
Replies: 3 comments 3 replies
-
|
Beta Was this translation helpful? Give feedback.
-
Hi there, The maintainers have labeled this discussion as a use case specific to "enterprise" users. Enterprise users typically self-host Renovate and have advanced requirements like custom certificates, HTTP proxies, private registries, air gapping, etc. Such cases usually need a lot of back-and-forth to resolve, because the problem is related to the user's environment. Usually the user's environment can not be reproduced publicly, which means that maintainer debugging is not possible. The maintainers decided their time is best spent on issues that help large numbers of users. This means enterprise-specific issues affecting one user (or a small number of users), are not a priority. If we can help you quickly, we will. But if you see this message, then a maintainer believes this is not a quick fix. The maintainers will not actively work on this issue, unless new information is found. If you are an enterprise user, please consider the following options:
If you choose to wait, then this discussion can remain open indefinitely. But please be patient, do not nudge or bump this discussion just to get attention. Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
-
Hi there, You redacted too much information from your config or logs. This makes it hard for us to pinpoint the problem. Please only redact truly sensitive information. Or consider an enterprise support contract, if Open Source support does not suit you. Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
-
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 SaaS, Renovate 38.142
Please tell us more about your question or problem
We are migrating from an on-premise Nexus, which did not require authentication for retrieving packages, to Google Artifact Registry, which does. Renovate was working successfully against Nexus.
The configuration below works for NPM packages and Docker images, but not for Gradle packages. This suggests to me that the credentials themselves are correct, but something in the configuration is not quite right.
We get 401 errors, for both gradle plugins and regular libraries. Java libraries from Maven Central are found no problem.
I have masked the project-name, company-name and gitlab-id but all other config is an exact representation.
Renovate runner config:
Target project renovate.json:
{ "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": ["local><gitlab-id>/renovate-config/renovate-config//config/default.json"], "packageRules": [ { "matchPackageNames": ["com.<company-name>**"], "matchDatasources": ["maven","gradle"], "registryUrls": ["https://europe-west2-maven.pkg.dev/<project-name>/gradle-all"] } ] }
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions