|
||||||||
|
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/groups/opt_out.
The problem is that this is configuration issue (yesterday I hadn't time to explain it all)
I have another Jenkins installation (that I need to switch off) on a Ubuntu Linux 10.04 working against the same repository and it works fine with the same repo.
The problem is that, for some reason, the Subversion plugin within Jenkins, is working on an incorrect encoding, contrary to the OS environment and Jenkins settings. I have managed to pass proper values ('UTF-8') to "file.encoding" and "sun.jnu.encoding" at Jenkins command line and it now displays accented words properly (like my name "José Luis Vázquez González") BUT the subversion plugin does NOT use this config and checkouts the repository in something non UTF-8 (Latin1 maybe?)
It is NOT a Subversion plugin version problem either. I tested the same version that was working on the other server and it failed as well.
I am sure it is a subversion plugin configuration or environment problem, and JUST in that plugin. (Remember, the svn and jsvn command line tools executed as the jenkins user will work just fine, checking out "descripción.txt" as expected)
How can I FORCE the subversion plugin to use UTF-8 instead of whatever it is using now?