Custom regex-manager is not being executed #26072
-
How are you running Renovate?Self-hosted If you're self-hosting Renovate, tell us what version of Renovate you run.37.78.1 If you're self-hosting Renovate, select which platform you are using.Azure DevOps (dev.azure.com) What is your question?I am trying to accomplish a setup where Renovate will detect version updates for tasks in Azure DevOps pipelines (yaml-files), including tasks that we created our self. I then added a custom manager and a custom datasource in my configuration:
However, when executing Renovate, the custom regex manager and/or custom dataSource is not being executed. Looking at the debug output, I believe the What am I missing? Logs (if relevant)Logs
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 11 replies
-
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 |
Beta Was this translation helpful? Give feedback.
-
I've added a minimal reproduction repo to demonstrate the problem: https://dev.azure.com/humanprinter/PublicRepos/_git/RenovateReproduction The pipeline that holds the output is located here: https://dev.azure.com/humanprinter/PublicRepos/_build/results?buildId=1295&view=results |
Beta Was this translation helpful? Give feedback.
I finally found the problem. It turned out to be the matchStrings-regex after all. The reason I did not found it at first, was that after migrating by reproduction repo to GitHub, I did not change the config.js (by mistake). It was therefore still looking at the code in my public Azure DevOps repo. Therefore, all changes I made in the GitHub repo did not have any effect.
Anyway, I managed to fix the regex and it now works as expected.