[JIRA] (JENKINS-24138) Archived file names can change when moved from slave to master

xrepiv@gmail.com (JIRA)

unread,

Jun 27, 2018, 5:59:01 AM6/27/18

to jenkinsc...@googlegroups.com

Joerg H commented on

JENKINS-24138

Re: Archived file names can change when moved from slave to master

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).

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

junk@jdark.com (JIRA)

unread,

Jul 18, 2019, 6:43:02 PM7/18/19

to jenkinsc...@googlegroups.com

Kim Abbott commented on

JENKINS-24138

Re: Archived file names can change when moved from slave to master

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.