Priority of customerManagers #34041
Replies: 4 comments 3 replies
-
|
I think you maybe have to use a different versioning. And, I don't think there's a |
Beta Was this translation helpful? Give feedback.
-
|
I'm currently using lookupNameTemplate for other custom managers, but I'll try changing it. What do you think in regards to use a different versioning? |
Beta Was this translation helpful? Give feedback.
-
|
Not sure, I willl have to look into it. But you should check how docker versioning currently handles the different versions and if it doesn't satisfy your use-case then try the |
Beta Was this translation helpful? Give feedback.
-
|
Also, I was wrong about But, are you sure the If the updates are fetched correctly, then try to fix the versioning (there should be logs for this as well) or paste your full logs then we can debug properly. |
Beta Was this translation helpful? Give feedback.
-
|
I looked at the supported versioning schemes found here https://docs.renovatebot.com/modules/versioning/#supported-versioning, and none of them seemed to match the container I'm having trouble with. I'm pretty sure it's because eclipse-temurin have chosen a non standard format :) Regading debugging if artifactory.compnay.com:5000 is needed to be part of the packageName. I'm not sure, it have been before for other customerManagers. But, as the custom Manager I've just created seems not to be used as it "overridden" by a default manager (I assume) I find it hard to debug it. Trying the regex versioning might be a possible way to go. I'll post an updated full log |
Beta Was this translation helpful? Give feedback.
-
|
[2025-02-05T12:24:02.776Z] Branch event |
Beta Was this translation helpful? Give feedback.
-
|
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:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. 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.
Container, 39.160.1
Please tell us more about your question or problem
In order to handle eclipse-temurin container versions like this one
eclipse-temurin:21.0.4_7-jre-windowsservercore-ltsc2022, I have created a customManager to handle the special version format.But as it is a container, it seems it's handled by a default manager instead of my newly created custom manager.
Is there any way I can prioritize my customManager? Maybe for specific containers only?
Maybe I'm trying to tackle this the wrong way. In the end, I want to have Renovate find the updates there are for eclipse-temurin, but as they are handling their versions the way they are, it seems Renovate is not able to find an updated version, even though the output when asking artifactory for versions of eclipse-temurin tells me there is a version 21.0.6_7 ready.
This is the custom manager I created
{
"customType": "regex",
"fileMatch": ["^Dockerfile$"],
"matchStrings": [
"artifactory\.company\.com:5000/(?[^:]+):(?\d+(?:\.\d+)*(?:[\._+]\d+)?)(?:-(?[^@\\s]+))?"
],
"datasourceTemplate": "docker",
"lookupNameTemplate": "artifactory.company.com:5000/{{depName}}",
"autoReplaceStringTemplate": "{{depName}}:{{newValue}}{{compatability}}"
}
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions