Unable to lookup Go modules in private projects in self-hosted GitLab #32125
-
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 Enterprise Edition v17.4.2-ee (self-hosted) / Renovate 38.130.2 Please tell us more about your question or problemOur organization self-hosts GitLab. All of our projects are private and are nested two groups deep (e.g. Previously (I'm not sure on what versions of GitLab / Renovate), Renovate was able to lookup Go modules in our private projects. At that time, we created a Since investigating the issue, I've changed the configuration slightly. I've set To investigate the issue, I've been running Renovate against a single project,
The project's module is Our matchHost: 'gitlab.appian-stratus.com',
token: process.env.RENOVATE_TOKEN Renovate correctly attempts to lookup the module directly from GitLab because
The issue, however, is that Renovate runs into a 404
While investigating this aspect of the issue, I noticed two things:
Another aspect of the issue is that, when creating branches for updates for public modules,
The important error here is:
The I found a few similar discussions (notably #30886 and #32105), but this issue looks a bit different. I also found a GitLab issue, but it's long been closed. I should also callout these GitLab docs on using projects as Go packages. They're mostly focused on the GitLab Go Proxy, which I don't think is relevant since I'm setting Is this a bug (in Renovate or in GitLab) or have I simply misconfigured something? I'm happy to provide additional logs / configs as needed. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 12 replies
-
Update: If I create a
The aforementioned GitLab docs lead me to believe that this aspect of the issue is do to improper Go request authentication |
Beta Was this translation helpful? Give feedback.
Hey @robbie-demuth,
when it comes to self-hosted GitLab with nested projects an Go, this can be a nightmare - I can absolutely understand your journey. We are successfully running this setup (despite a small issue we are currently facing), here is what we have configured:
Go environment variables
We want to make sure that our internal packages are not fetched via any proxy.
.netrc
for authentication part 1As you already mentioned this is re…