-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Windows XP slave. CentOS 5.5 server
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
- is duplicated by
-
JENKINS-13638 Copy artifacts occasionally fail
-
- Closed
-
-
JENKINS-13515 Copy failed on windows machine because of timestamp
-
- Closed
-
- is related to
-
JENKINS-10805 Preserve artifact timestamps during copy
-
- Closed
-
-
JENKINS-13551 Copy Artifact fails if selector class="hudson.plugins.copyartifact.StatusBuildSelector" is set
-
- Closed
-
-
JENKINS-14774 Failed to copy artifacts from another build job with timestamp exception
-
- Closed
-
[JENKINS-11073] copy artifact fails on windows XP slaves due to failing to set a timestamp
Assignee | Original: Alan Harder [ mindless ] | New: Kohsuke Kawaguchi [ kohsuke ] |
Link |
New:
This issue is related to |
kohsuke, can you take a look at this? I don't think copyartifact plugin should need to check the system type and avoid calling this API for windows..