[JIRA] (JENKINS-59645) Encoding problems after update to version 2.190.1

[jonathancsgoncalves@gmail.com (JIRA)]

Jonathan Gonçalves created an issue

Jenkins / JENKINS-59645 Encoding problems after update to version 2.190.1 Issue Type: Bug Assignee: Unassigned Attachments: Capturar.PNG, Capturar2.PNG, image (3).png Components: _unsorted Created: 2019-10-03 14:33 Environment: Docker Image: jenkins / jenkins : 2.190.1 Using Blueocean and all default plugins in the latest version Priority: Major Reporter: Jonathan Gonçalves 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. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[jonathancsgoncalves@gmail.com (JIRA)]

Jonathan Gonçalves commented on JENKINS-59645

Re: Encoding problems after update to version 2.190.1 Added some error logs

Add Comment

[jonathancsgoncalves@gmail.com (JIRA)]

Jonathan Gonçalves updated an issue

Jenkins / JENKINS-59645

Encoding problems after update to version 2.190.1

Change By: Jonathan Gonçalves Attachment: jenkins.log

Add Comment

[jonathancsgoncalves@gmail.com (JIRA)]

Jonathan Gonçalves updated an issue

Jenkins / JENKINS-59645 Encoding problems after update to version 2.190.1 Change By: Jonathan Gonçalves

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.

Add Comment

[ian.williams1@telus.com (JIRA)]

Ian Williams commented on JENKINS-59645

Re: Encoding problems after update to version 2.190.1 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.

Add Comment