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

Encoding problems after update to version 2.190.1

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: _unsorted
    • Labels:
      None
    • Environment:
      Docker Image: jenkins / jenkins : 2.190.1
      Using Blueocean and all default plugins in the latest version
    • Similar Issues:

      Description

      After update from 2.176.1 to 2.190.1 some projects with accents can't be access anymore because the Job link appears empty. 

      Another problem is in Blueocean, that doesnt show project names with accents.

      Another problem is in the job execution, that throw an Exception when try to build projects with accents on name.

       

      EDIT: Tested same things on 2.176.4 version and none of these errors occours.

        Attachments

        1. Capturar.PNG
          Capturar.PNG
          39 kB
        2. Capturar2.PNG
          Capturar2.PNG
          9 kB
        3. image (3).png
          image (3).png
          42 kB
        4. jenkins.log
          53 kB

          Activity

          Hide
          jonjoncs Jonathan Gonçalves added a comment -

          Added some error logs

          Show
          jonjoncs Jonathan Gonçalves added a comment - Added some error logs
          Hide
          ianw Ian Williams added a comment -

          You are reporting multiple problem on a single JENKINS-ISSUE. Have you confirmed they have the same Cause ?

          Otherwise, you should probably be referencing them separately, especially as I ended up here from the reference in the LTS Changelog.

          Even if they are found to have the same root cause, it is probably better to have separate issues and then link the issues, just in case.

          Show
          ianw Ian Williams added a comment - You are reporting multiple problem on a single JENKINS-ISSUE. Have you confirmed they have the same Cause ? Otherwise, you should probably be referencing them separately, especially as I ended up here from the reference in the LTS Changelog . Even if they are found to have the same root cause, it is probably better to have separate issues and then link the issues, just in case.

            People

            • Assignee:
              Unassigned
              Reporter:
              jonjoncs Jonathan Gonçalves
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: