• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • 2.398

      I try the following test code on http://job-dsl.herokuapp.com/
      ```
      organizationFolder('test')

      { displayName('Foxy 🦊') }

      ```
      it works the generated xml is correct.

      On my container i debug with cat the char is correct in the jenkins.yaml
      file /jenkins.yaml
      /jenkins.yaml: UTF-8 Unicode text

      cat jenkins.yaml | grep displayName
      ```
      displayName('Foxy (🦊)')
      ```
      the generated config.xml from the job the char is broken
      ```
      cat /var/jenkins_home/jobs/test/config.xml | grep display
      <displayName>Foxy (力)</displayName>
      ```

      when i set the displayName manual over the gui it works and also the char in the config.xml is correct.

          [JENKINS-69129] DisplayName and unicode character

          Is there any known workaround or progress on this?

          We would love to see this fixed as well.

           

          Best,

          Patrick

          Patrick Kulling added a comment - Is there any known workaround or progress on this? We would love to see this fixed as well.   Best, Patrick

          Just to add to the above point on what I have tried so far:

          1. Creating a config.xml using the standalone jar

          This just works.

          1. Download the standalone jar, see: https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves#run-a-dsl-script-locally
          2. Generate the config.xml as described in the wiki

          The generated config.xml does display the emoji correctly

           

          2. Cloning the git repository & validating the issues via tests

          I have also tried to clone the project https://github.com/jenkinsci/job-dsl-plugin and to confirm the broken behaviour via a unit test without any success. The test is passing just fine.

           

          The only way to 100% reproduce the issue is on the jenkins instance itself.

          As a side note: You won't be able to see the issue in all the cases when browsing https://url-of-your-jenkins/job/job-name/config.xml but only when downloading the file and when opening it in an editor.

          Patrick Kulling added a comment - Just to add to the above point on what I have tried so far: 1. Creating a config.xml using the standalone jar This just works. Download the standalone jar, see: https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves#run-a-dsl-script-locally Generate the config.xml as described in the wiki The generated config.xml does display the emoji correctly   2. Cloning the git repository & validating the issues via tests I have also tried to clone the project https://github.com/jenkinsci/job-dsl-plugin and to confirm the broken behaviour via a unit test without any success. The test is passing just fine.   The only way to 100% reproduce the issue is on the jenkins instance itself. As a side note: You won't be able to see the issue in all the cases when browsing https://url-of-your-jenkins/job/job-name/config.xml  but only when downloading the file and when opening it in an editor.

          Gordon Franke added a comment -

          Anyone that find a workaround?

          Best Gordon

          Gordon Franke added a comment - Anyone that find a workaround? Best Gordon

            basil Basil Crow
            gimler Gordon Franke
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: