|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm not comfortable to English. Just excuse me.
The simplest walkaround is choosing JGit(not git.exe)to Git installations.
CliGitAPIImpl launches external get.exe executables and get log messages via stdout stream.(in CliGitAPIImpl.java,line 648~660)
the "git.exe" print changelog with UTF-8 encoding. It seems to that the launcher (or something in MS Windows) assumes that message is encoded in OS's current encoding (CP949 in my case) and try to convert it from CP949 to Unicode, so making normal UTF8 text to garbled text. Finally, CliGitAPIImpl get this garbled text.
I don't know exactly what is doing that bad converting yet, but some test might give me a tiny clues.
In Powershell, doing like below get the same garble text.
D:\git\cloned> git.ext whatchanged --no-abbrev -M --pretty=raw > Idontlikethis.txt
Adding --encoding option make git.ext to print with given encoding, and doing so like below will get correct message. Test with your launages' encoding.
D:\git\cloned> git.ext whatchanged --no-abbrev -M --pretty=raw --encoding=cp949 > IwantThis.txt