-
Improvement
-
Resolution: Won't Fix
-
Minor
-
None
calling recordIssues configured with 'failOnError: true' will abort my build if any file containing a defect has wrong encoding while fingerprinting
[-ERROR-] - '<path>', provided encoding 'UTF-8' seems to be wrong
I got this issue with clang-tidy and cppcheck tool.
Is there any way to keep the failOnError behaviour for real errors like missing file or parse errors and to ignore encoding or at least have this only as a warning?