• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • warnings-plugin
    • None

      All the text shown by the plugin suffers from a UTF-8 as ASCII encoding error.
      This is particularly annoying as GCC is outputting fancy quotes.

      For example: unused variable ‘n’

          [JENKINS-16929] GNU make + GCC parser can't handle UTF-8

          Ulli Hafner added a comment -

          Are you parsing the content of a file or from the console log? Did you specify the encoding in the project configuration?

          Ulli Hafner added a comment - Are you parsing the content of a file or from the console log? Did you specify the encoding in the project configuration?

          James Howe added a comment -

          Parsing from console log.
          In "Console output" (and the raw view) they display correctly as ‘ and ’.
          The project configuration has no encoding options that I can see.

          James Howe added a comment - Parsing from console log. In "Console output" (and the raw view) they display correctly as ‘ and ’. The project configuration has no encoding options that I can see.

          Ulli Hafner added a comment -

          The option is in the advanced section of the warnings publisher.

          Is the console always shown in UTF-8? Then I will always set the encoding to UTF-8 for the console (and ignore the setting in the configuration).

          Ulli Hafner added a comment - The option is in the advanced section of the warnings publisher. Is the console always shown in UTF-8? Then I will always set the encoding to UTF-8 for the console (and ignore the setting in the configuration).

          James Howe added a comment -

          All Jenkins content is served with charset=UTF-8 in the Content-Type, so I guess that's a yes.

          James Howe added a comment - All Jenkins content is served with charset=UTF-8 in the Content-Type, so I guess that's a yes.

          Ulli Hafner added a comment -

          Hmm, I'm reading the actual file that is used to render the console log. This file seems to have no UTF-8 encoding header. Maybe that output depends on your build tool and can handle different encodings.

          So I would prefer not to change the current behavior: you just need to set the encoding entry in the job configuration of the warnings plugin (the second last entry in the advanced section).

          Ulli Hafner added a comment - Hmm, I'm reading the actual file that is used to render the console log. This file seems to have no UTF-8 encoding header. Maybe that output depends on your build tool and can handle different encodings. So I would prefer not to change the current behavior: you just need to set the encoding entry in the job configuration of the warnings plugin (the second last entry in the advanced section).

          James Howe added a comment -

          I would imagine it's globally set somewhere near the Winstone level. Everything that Jenkins serves is marked as UTF-8, including your plugin's output.
          At minimum the default should be UTF-8, without having to go through every job config and set it manually.

          James Howe added a comment - I would imagine it's globally set somewhere near the Winstone level. Everything that Jenkins serves is marked as UTF-8, including your plugin's output. At minimum the default should be UTF-8, without having to go through every job config and set it manually.

          Ulli Hafner added a comment -

          Yes, that is correct: what Jenkins serves is UTF-8. But I'm reading the raw output of the build! And that output seems to be build related.

          I think that I can try to switch to UTF-8 for the console log and see if others complain about that

          Ulli Hafner added a comment - Yes, that is correct: what Jenkins serves is UTF-8. But I'm reading the raw output of the build! And that output seems to be build related. I think that I can try to switch to UTF-8 for the console log and see if others complain about that

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          src/main/java/hudson/plugins/warnings/WarningsPublisher.java
          http://jenkins-ci.org/commit/warnings-plugin/5934c43401b60d239f6a8820e15ee67be5c5afc7
          Log:
          [FIXED JENKINS-16929] Use UTF-8 encoding when parsing the console log.


          You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
          To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com.
          For more options, visit https://groups.google.com/groups/opt_out.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/WarningsPublisher.java http://jenkins-ci.org/commit/warnings-plugin/5934c43401b60d239f6a8820e15ee67be5c5afc7 Log: [FIXED JENKINS-16929] Use UTF-8 encoding when parsing the console log. – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out .

            drulli Ulli Hafner
            jameshowe James Howe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: