[
https://issues.jenkins-ci.org/browse/JENKINS-12412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162019#comment-162019
]
Alexander Dvorsky edited comment on JENKINS-12412 at 4/25/12 11:55 AM:
-----------------------------------------------------------------------
Thanks a lot. I will give it a try with 1.20.
just tried it. works. this problem does not occur with 1.20
was (Author: advorsky73):
Thanks a lot. I will give it a try with 1.20.
> copyartifact 1.21 fails in at least certain cross-platform copy scenarios
> -------------------------------------------------------------------------
>
> Key: JENKINS-12412
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12412
> Project: Jenkins
> Issue Type: Bug
> Components: copyartifact
> Reporter: oeuftete
> Assignee: Kohsuke Kawaguchi
> Priority: Critical
> Attachments: System Information [Jenkins].html
>
>
> Moved from Copy Artifact 1.20 to 1.21 today, and was greeted with a
> build-breaking bug. Basic scenario: Windows master, two linux slaves. Build
> A runs on slave and generates artifact foo/bar.txt . Build B runs and copies
> the artifacts from build A into directory A-artifacts. A-artifacts directory
> ends up with a file "foo\bar.txt" (with a literal backslash in the file
> name), instead of directory "foo" containing file "bar.txt".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
