How to fail on compilation errors when running Polyspace Bug Finder in CI?

We found that our CI (using the polyspace-configure and polyspace-bug-finder commands) has not detected some issues so we ran the analysis locally in the GUI app and found that a compilation error was shown in the output.

The errors are written to the analysis .log file and it is mentioned in the report that the compilation for the files failed but i would have expected that the "polyspace-bug-finder" execution would exit with !=0 or that this treated as a dedicated defect in such cases as this renders the analysis results useless.

So my question is: how to automatically detect such compilation errors when using the commandline apps?

Answer 1

[Peter Bauer]

sorry for the noise, found -stop-if-compile-error: https://de.mathworks.com/help/bugfinder/ref/stopanalysisifafiledoesnotcompilestopifcompileerror.html