Search code examples
azurenpmazure-devopsazure-pipelinesmkdocs

How do I keep Azure DevOps from treating infos and warnings as errors in my pipeline?

I am working on an Azure DevOps pipeline created without YAML. In the pipeline, node.js and npm are used to build some web interfaces. mkdocs is used to build web documentation. My problem is that Azure DevOps treats some infos and warnings as errors:

4 erros of information and warning statements

While the build does not fail, it is marked as only partially successful. I prefer to have a clean build.

How do I keep Azure DevOps from treating infos and warnings as errors? Or is it some setting I have to configure on the side of mkdocs and npm?

Solution

  • It seems that the company firewall prevented npm from making ssl connections because of missing certificates or something. I added

    npm set strict-ssl false

    to the build pipeline which -ironically- makes the connection less secure, but it makes all errors go away which I prefer to suppressing the errors/warnings/info.

    I don't know if Don't Fail on Standard Error would even do anything since the build did not fail, it was partially successful. I prefer to have it checked in case a real error occurs.

    After looking at it some more I am not exactly sure the highlighting and specification of errors is correct in the pipeline results. Why would an info output be marked as error anyway?