Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-69038

wrong source file encoding fails build

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • warnings-ng-plugin
    • 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?

       

            drulli Ulli Hafner
            thebro Kevin Broselge
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: