customManagers with enabledManagers #25898
Replies: 3 comments 1 reply
|
Does this maybe have a connection to the still open points in this issue: #19066 ? |
1 reply
|
I provided all enbaledManagers as CLI-Options, because otherwise regex would be migrated to custom.regex So with renovate --dry-run --enabled-managers "regex","custom","custom.regex" I get the following config: With the same behavior as before: |
0 replies
|
Ah, I have to apologize! The error was on my side, my matchString regex was faulty, which lead to the error encountered. Thank you very much for your support nevertheless. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us what version of Renovate you run.
37.64.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
I have a special use case, where I want to use only a custom regex manager with renovate.
For this I defined my custom manager as documented:
and used the
"enabledManagers": ["custom.regex"],to let renovate only use the created custom manager.But this leads to some irritating behavior, as seen in the logs.
The fileMatch works just fine and finds the files I tell him to, but afterwords, he doesn't extract the dependencies.
I checked the matchStrings regex multiple times and there doesn't seem to be an error either.
What would be a viable configuration to achieve the same result?
Relevant debug logs
Logs
Have you created a minimal reproduction repository?
Placeholder value, please select the correct response from the dropdown
All reactions