[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
Markus Unterauer commented on JENKINS-11073 copy artifact fails on windows XP slaves due to failing to set a timestamp In jenkins v1.474 this problem is still there. Overwriting existing files does not work, writing new files works fine. So I use the following workaround: Use a Execute Windows batch command to delete all files before copying. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
Kohsuke Kawaguchi resolved JENKINS-11073 as Fixed copy artifact fails on windows XP slaves due to failing to set a timestamp I think this is a manifestation of the same issue that caues JENKINS-11251. I claim this change in remoting fixes this. This commit will be a part of 1.473. Notice that all the problem reports in this bug is about remoting. Due to the asynchrony in the read/write operations in remoting vs closure calls, it was possible that the attempt to set the timestamp happens before the file is fully is written (or even before the write starts at all.) Change By: Kohsuke Kawaguchi (30/Jun/12 1:05 AM) Status: Reopened Resolved Assignee: Alan Harder Kohsuke Kawaguchi Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
kutzi commented on JENKINS-11073 copy artifact fails on windows XP slaves due to failing to set a timestamp @Nicolas: I don't understand, why you are not simply using FilePath.copyToWithPermission? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
kutzi edited a comment on JENKINS-11073 copy artifact fails on windows XP slaves due to failing to set a timestamp It should be fixed in 1.447 and higher http://jenkins-ci.org/changelog This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
kutzi commented on JENKINS-11073 copy artifact fails on windows XP slaves due to failing to set a timestamp It should be fixed in 1.446 and higher http://jenkins-ci.org/changelog This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
kutzi commented on JENKINS-11073 copy artifact fails on windows XP slaves due to failing to set a timestamp Nicolas, yes there seems to be a bug in JDK with respect to setting the timestamp on Windows. However, that should be worked around in Jenkins core now. Bertrand, Denis, Alexander, Marnix: which Jenkins version are you using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
kutzi assigned JENKINS-11073 to Alan Harder copy artifact fails on windows XP slaves due to failing to set a timestamp Change By: kutzi (17/Jun/12 12:12 PM) Assignee: kutzi Alan Harder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
[ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162649#comment-162649 ] gleb bahmutov commented on JENKINS-11073: - Problem resolved by installing Java JRE 7 (1.7) > 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 131655226" > 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
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
[ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162476#comment-162476 ] Jose Sa commented on JENKINS-11073: --- I found a workaround for this problem, by updating Java to version 1.7 in Windows XP Slave, as advised in the this [java bug report|http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=f26e4ae1bfef1b1484f3fea00f61?bug_id=6357599] > 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 131655226" > 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
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
[ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162145#comment-162145 ] Marnix Klooster commented on JENKINS-11073: --- Same problem here with 1.22, not with 1.21. Master and slave both run on Windows Server 2008 R2. If you need additional info, just ask. > 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 131655226" > 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
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
[ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161883#comment-161883 ] Alexander Dvorsky commented on JENKINS-11073: - I can confirm this too. Rolling back to 1.21 fixes the problem. Slave having the problem is Windows 7. Master is Windows 7 too. StackTrace: ERROR: Artefaktekopie aus mit Filter: ** fehlgeschlagen hudson.util.IOException2: Failed to copy C:\Jenkins\jobs\\builds\2012-04-22_22-02-00\archive\Build\\File.xrs to c:\\Build\\File.xrs at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:91) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyAll(FingerprintingCopyMethod.java:63) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:243) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:215) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475) at hudson.model.Run.run(Run.java:1421) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: hudson.util.IOException2: remote file operation failed: c:\\Build\\File.xrs at hudson.remoting.Channel@d1faace:BuildSlaveWindows at hudson.FilePath.act(FilePath.java:828) at hudson.FilePath.act(FilePath.java:814) at hudson.FilePath.touch(FilePath.java:1160) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:79) ... 12 more Caused by: java.io.IOException: Failed to set the timestamp of c:\\Build\\File.xrs to 1335126036000 at hudson.FilePath$19.invoke(FilePath.java:1166) at hudson.FilePath$19.invoke(FilePath.java:1160) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Build step 'Artefakte aus einem anderen Projekt kopieren' marked build as failure > 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 131655226" > 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
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
[ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Kniazhev reopened JENKINS-11073: -- > 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 131655226" > 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
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
[ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161880#comment-161880 ] Denis Kniazhev edited comment on JENKINS-11073 at 4/23/12 8:10 AM: --- I can also confirm that the issue is back with version 1.22 of 'Copy Artifact plugin'. Rolling back to 1.21 fixes the problem Please re-open was (Author: denisk): I can also confirm that the issue is back with version 1.22 of 'Copy Artifact plugin'. Rolling back to 1.21 fixes the problem > 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 131655226" > 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
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
[ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161880#comment-161880 ] Denis Kniazhev commented on JENKINS-11073: -- I can also confirm that the issue is back with version 1.22 of 'Copy Artifact plugin'. Rolling back to 1.21 fixes the problem > 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 131655226" > 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
[JIRA] (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp
[ 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 131655226" > 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
