Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
Tested on Ubuntu and RHEL6. Currently using Jenkins 1.553 but the issue would be present in all current versions. The server runs in WebSphere Liberty Profile 8.5.5.1 and 8.5.5.2 and Java is an IBM JDK 1.6.0
Description
I have a Jenkins set up that uses slaves and archives files after a build. What I've found is that if there is a file that uses multi-byte characters in the name (like 日本語ファイル) then the name gets altered when uploaded to the Jenkins master. Using the master node does not have the issue, so I did some research and found that the problem actually lies in the version of Ant that is being used (1.8.3) and how it reads file names and converts the multi-byte characters down to one byte. It looks like the issue was fixed in Apache Ant 1.9.0
Attachments
Issue Links
- is duplicated by
-
-
- Resolved
-
Activity
I too am still having this issue. Running with:
Jenkins 2.176.1
Copy Artifact Plugin 1.42.1
Master Linux
Slave Windows 8 Server
File pulls from repo onto Windows slave with correct filename, but when archived back to master the ™ gets garbled. So the rest of my deploy steps fail because I now have a file with an invalid filename.
Its unclear if any changes from 2014 were ever implemented? Even version 1.9.0 is pretty dated, so seems like core is due to update and update dependencies? I don't know of any workaround at this point.
This article presented a good workaround for this issue. Worked for me.
Thank you, looks promising, will take a look.
Did you add this via global properties or via EnvInject API Plugin?
I just followed article guidelines and used Windows env variables .
Four years later, I still have this Issue in 2.121.1 when archiving artifacts from a Linux agent (file.encoding UTF-8, sun.io.unicode.encoding UnicodeLittle, sun.jnu.encoding UTF-8) to a Windows master (file.encoding Cp1252, sun.io.unicode.encoding UnicodeLittle, sun.jnu.encoding Cp1252).