GitLab CI/CD components and $CI_SERVER_HOST

[mueller-ma]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us what version of Renovate you run.

37.202.2

If you're self-hosting Renovate, select which platform you are using.

GitLab self-hosted

Was this something which used to work for you, and then stopped?

I have not seen this working

Describe the problem

GitLab CI/CD components are supported by Renovate: #23431

However when I use $CI_SERVER_HOST (like here: #23431 (comment)) to use components on my self-hosted GitLab, Renovate fails:

DEBUG: GET https://$CI_SERVER_HOST/api/v4/projects/<redacted>/repository/tags?per_page=100 = (code=ENOTFOUND, statusCode=-1 retryCount=2, duration=1) (repository=<redacted>)
DEBUG: Gitlab API error (repository=<redacted>)
       "err": {
         "name": "RequestError",
         "code": "ENOTFOUND",
         "timings": {
           "start": 1708434750550,
           "socket": 1708434750550,
           "lookup": 1708434750550,
           "error": 1708434750551,
           "phases": {"wait": 0, "dns": 0, "total": 1}
         },
         "message": "getaddrinfo ENOTFOUND $ci_server_host",

I included the following code in my Renovate config and I can see in the logs that the alias is loaded:

  "registryAliases": {
    "$CI_REGISTRY": "<redacted>",
    "$CI_SERVER_HOST": "<redacted>"
  },

Relevant debug logs

Logs

Copy/paste the relevant log(s) here, between the starting and ending backticks

Have you created a minimal reproduction repository?

Placeholder value, please select the correct response from the dropdown

[ad-mcas]

Hi,

I have the same error with Renovate ghcr.io/renovatebot/renovate:37.227.1

We use $CI_SERVER_HOST into component url (see example below) because we shared same code between multiple self-hosted gitlab.

example on a gitlab-ci.yml

include:
  - component: $CI_SERVER_HOST/commun/cicd_components/docker-image/docker-image-build-quality-and-test@0.0.4-beta

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this.

To get started, please read our guide on creating a minimal reproduction.

We may close the discussion if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.

Good luck,

The Renovate team

[ad-mcas]

I have do this project for minimal reproduction: https://gitlab.com/ad_mcas/test-project
I hope its ok for you.

[viceice]

please transfer to GitHub

[ad-mcas]

imported to github: https://github.com/ad-mcas/test-project
But I don't know how to test on github

[ad-mcas]

@mueller-ma
The GitLab CI manager did not support aliases. With new version of renovate, the problem is fixed (by #28607)

Personally I use this config.js file to to easily indicate the registry aliases:

module.exports = {
    $schema: "https://docs.renovatebot.com/renovate-schema.json",
        "registryAliases": {
          "$CI_SERVER_FQDN": process.env.CI_SERVER_FQDN,
          "$CI_SERVER_HOST": process.env.CI_SERVER_HOST,
          "$CI_REGISTRY": process.env.CI_REGISTRY
        }
  }