[
https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161784#comment-161784
]
Bertrand Latinville commented on JENKINS-11073:
-----------------------------------------------
Seems that this issue is back with version 1.22.
I have just upgraded and faced the problem on a job.
Failed 4 times with this error.
Rolling back to 1.21 and the job is passed.
> copy artifact fails on windows XP slaves due to failing to set a timestamp
> --------------------------------------------------------------------------
>
> Key: JENKINS-11073
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11073
> Project: Jenkins
> Issue Type: Bug
> Components: copyartifact, core
> Affects Versions: current
> Environment: Windows XP slave. CentOS 5.5 server
> Reporter: Jeff Koenig
> Assignee: kutzi
> Attachments: copyArtifact.txt
>
>
> The copy artifact build step fails when it trys to set the time stamp on
> windows XP slaves. I have attached the stack trace that shows this error
> "Caused by: java.io.IOException: Failed to set the timestamp of
> C:\automation\AccuNurse-3.2.0.0-569-upgrade.zip to 1316552260000"
> I believe this issue was caused by the changes made for JENKINS-10805.
> I have also found a discussion of others experiencing the same issue
> http://groups.google.com/group/jenkinsci-users/browse_thread/thread/249ebeb0660d5e0d/e831b70f5688d0c4?show_docid=e831b70f5688d0c4
--
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
