JENKINS-75956: Add charset support to readFileFromWorkspace function
#1605
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I tried to upgrade Jenkins using Java from 17 to 21 at Windows, I got an error due to 'JEP 400: UTF-8 by Default'. To work around this issue, we can use '-Dfile.encoding=COMPAT' or convert all files you load to UTF-8, but I would like to be able to solve this problem just with this plugin.
The bug is the belief that when processing text files in Java, I should specify the character encoding.
JENKINS-75956: https://issues.jenkins.io/browse/JENKINS-75956
Submitter checklist