Enhance support of GitLab CI/CD components #30919
Cquad
started this conversation in
Suggest an Idea
Replies: 2 comments 7 replies
-
Use registryAliases |
Beta Was this translation helpful? Give feedback.
1 reply
-
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. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Tell us more.
Since this Pull Request GitLab CI/CD component has been updated to switch from an hard-coded registry url to a GitLab instance variable.
See official documentation about GitLab CI/CD component : https://docs.gitlab.com/ee/ci/components/index.html#use-a-component
Using
$CI_SERVER_FQDN
in component isn't compatible with renovate.You can find a project example with an outdated component : https://gitlab.com/cedric3.olivier/renovate-cicd-components-4/-/blob/main/.gitlab-ci.yml
As you can see in component documentation, it's recommended to use
$CI_SERVER_FQDN
: https://gitlab.com/explore/catalog/gitlab-org/components/danger-reviewWhen running renovate on this project, CI_SERVER_FQDN is not evaluated if
renovate.json
doesn't have registryAliases sectionminimal reproduction repository
link to a minimal reproduction on gitlab.com
Beta Was this translation helpful? Give feedback.
All reactions