Return an error if a custom manager does not match with regex

[bdovaz]

Tell us more.

It has happened to us that a custom manager we have with a regex has started to fail silently because we have changed the format of the file that checks and it makes the regex no longer match but as it does not fail renovate it is not easy to see this problem.

It would be nice to be able to configure a custom regex manager so that it can fail if it does not find results.

[rarkins]

Fail exactly how? Eg log an error, abort the job, etc?

[rarkins]

Is there any existing debug, info or warn message which indicates that it didn't match anything?

[bdovaz]

Appears: “skipReason”: “invalid-value”.

This is as I say because the regex no longer matches what it should and fails.

But that's what I'm saying, you only see that if you look specifically at the logs but the renovate command itself doesn't fail, and what I would like is to be able to control in a granular way that if a regex fails I can make the command itself fail with exit code 1.

[rarkins]

So this idea definitely isn't by default, because it would mostly prevent custom managers from being in org/global config (any repo not containing a match would error).

What I think we could do is:

• Add a logger.debug message to explicitly say something like "custom manager did not find any results"
• Add a preset which uses logLevelRemap to remap this from debug to error

Then you could include this preset at either your global or repo level and then any time you have a custom manager which doesn't produce a result then you'd get a logger.error message which then causes a non-zero exit code

[bdovaz]

Sounds good @rarkins

Thanks!

[RahulGautamSingh]

renovate/lib/modules/manager/custom/regex/index.ts

Line 49 in 72a5af8

deps = deps.filter(is.truthy);

Adding a debug log here should do the job.
Same for jsonata manager as well.