Closed KaVeKa closed 4 months ago
π Hi, Thank you for reporting.
I'm wondering if we can catch this as in renovate
it's just an INFO:
as showed in the logs. π€
Thanks for the quick response!
I was also surprised to see that this was logged as INFO and not as WARN or ERROR.
However, there is clearly a structured error response from somewhere inside the renovate process. I don't know if that is accessible from somewhere in your plugin code.
Not sure if this maybe helps? https://docs.renovatebot.com/config-validation/
Seems like an additional command/call that can be ran to validate the renovate config which returns a non-zero exit code?
Okay π
You can probably add this step in your yaml
? π
I wouldn't know how? Can we directly call that config-validation command from the Azure DevOps pipeline? I assume that it can more easily be ran from the index.ts file in your task?
The thing is that I'm not use Azure for a long time now. So I can't really test it... If you do the PR, I can try to build and publish and see if it's working for you?
If not, adding on your yaml
, would look like:
pool:
name: Azure Pipelines
vmImage: ubuntu-latest
variables:
- name: LOG_LEVEL
value: debug
- name: System.Debug
value: true
steps:
- task: geeklearningio.gl-vsts-tasks-yarn.yarn-installer-task.YarnInstaller@3
displayName: 'Use Yarn 1.x'
- task: NodeTool@0
displayName: 'Use Node 14.15.4'
inputs:
versionSpec: 14.15.4
# new stuff to add πππ
- task: CmdLine@2
inputs:
script: npx THE THING HERE TO ADD
- task: jyc.vsts-extensions-renovate-me.default-build-task.RenovateMe@0
displayName: Renovate
It took me a while to get back to, but I created a PR :) I based myself on the renovate documentation: https://docs.renovatebot.com/config-validation/
It doesn't build on my MAC. I'll try thiw week on windows π€
Should be in 1.0.3
. Let me know. π₯³
Describe the bug When the renovate.json configuration file is invalid, the renovate Azure DevOps pipeline does not fail, but reports that everything went OK.
Maybe there is some configuration in the pipeline we are missing?
To Reproduce Steps to reproduce the behavior:
Expected behavior The Azure DevOps Pipeline fails
Screenshots![image](https://github.com/jycouet/VSTSExtensions/assets/8722437/08fd67f9-a44c-45c9-8a92-c1c5f5b2761a)
Additional context Here is the logging output from the pipeline task: