[JIRA] Created: (JENKINS-11073) copy artifact fails on windows XP slaves due to failing to set a timestamp

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: Alan Harder
         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Harder reassigned JENKINS-11073:
-------------------------------------

    Assignee: Kohsuke Kawaguchi  (was: Alan Harder)

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

> 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: Kohsuke Kawaguchi
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153237#comment-153237 ]

b2jrock commented on JENKINS-11073:
-----------------------------------

I see this also on Win2008R2/x64, but only occasionally when copying artifacts from an upstream job. Stack trace is pretty much the same as the attached one.

> 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: Kohsuke Kawaguchi
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153289#comment-153289 ]

Conny Kreyßel commented on JENKINS-11073:
-----------------------------------------

Same here, we rolled back to jenkins 1.427 and all works fine.

> 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: Kohsuke Kawaguchi
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153487#comment-153487 ]

j f commented on JENKINS-11073:
-------------------------------

I also have this problem.  Windows XP slave and jenkins server (currently 1.432) on debian 6

> 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: Kohsuke Kawaguchi
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153487#comment-153487 ]

j f edited comment on JENKINS-11073 at 9/28/11 8:59 AM:
--------------------------------------------------------

I also have this problem.  Windows XP slave and jenkins server (currently 1.432) on debian 6
(the same job worked before, but stopped working around versions 1.428 to 1.430)

      was (Author: jfbos):
    I also have this problem.  Windows XP slave and jenkins server (currently 1.432) on debian 6
 

> 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: Kohsuke Kawaguchi
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153488#comment-153488 ]

dan russell commented on JENKINS-11073:
---------------------------------------

Just tried to upgrade from 1.424 to 1.432 and experienced this issue

> 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: Kohsuke Kawaguchi
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153560#comment-153560 ]

Luke Last commented on JENKINS-11073:
-------------------------------------

I had the same problem with Jenkins 1.432 and Copy Artifact Plugin 1.18, rolled back to Copy Artifact Plugin 1.16 to avoid 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: Kohsuke Kawaguchi
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153568#comment-153568 ]

j f commented on JENKINS-11073:
-------------------------------

Thanks for the hint luke, rolling back to copyartifact plugin manually to 1.16 also helped me too.
(you can get it here: http://updates.jenkins-ci.org/download/plugins/copyartifact/)

> 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: Kohsuke Kawaguchi
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155116#comment-155116 ]

pancake commented on JENKINS-11073:
-----------------------------------

*Will the bug be ever fixed?*
We're experiencing this nasty bug on Windows Server 20003 R2 SP2 x64 starting from I guess 1.429 (1.428 works fine).
We've tried several newer versions including 1.437 \- the bug is still there :(


{quote}
13:10:54  ERROR: Failed to copy artifacts from XXX with filter: build/YYY.*.zip
13:10:54  hudson.util.IOException2: remote file operation failed: C:\_JenkinsCI\workspace\ZZZ\YYY.ABCD.zip at hudson.remoting.Channel@581d0d:hudson32
13:10:54   at hudson.FilePath.act(FilePath.java:781)
13:10:54   at hudson.FilePath.act(FilePath.java:767)
13:10:54   at hudson.FilePath.touch(FilePath.java:1063)
13:10:54   at hudson.FilePath.copyToWithPermission(FilePath.java:1429)
13:10:54   at hudson.plugins.copyartifact.FilePathCopyMethod.copyOne(FilePathCopyMethod.java:58)
13:10:54   at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:231)
13:10:54   at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:200)
13:10:54   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
13:10:54   at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:694)
13:10:54   at hudson.model.Build$RunnerImpl.build(Build.java:178)
13:10:54   at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
13:10:54   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:460)
13:10:54   at hudson.model.Run.run(Run.java:1404)
13:10:54   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
13:10:54   at hudson.model.ResourceController.execute(ResourceController.java:88)
13:10:54   at hudson.model.Executor.run(Executor.java:230)
13:10:54  Caused by: java.io.IOException: Failed to set the timestamp of C:\_JenkinsCI\workspace\ZZZ\YYY.ABCD.zip to 1320516545963
13:10:54   at hudson.FilePath$17.invoke(FilePath.java:1068)
13:10:54   at hudson.FilePath$17.invoke(FilePath.java:1063)
13:10:54   at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2022)
13:10:54   at hudson.remoting.UserRequest.perform(UserRequest.java:118)
13:10:54   at hudson.remoting.UserRequest.perform(UserRequest.java:48)
13:10:54   at hudson.remoting.Request$2.run(Request.java:287)
13:10:54   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
13:10:54   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
13:10:54   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
13:10:54   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
13:10:54   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
13:10:54   at java.lang.Thread.run(Thread.java:619)
13:10:54  Build step 'Copy artifacts from another project' marked build as failure
{quote}
               

> 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: Kohsuke Kawaguchi
>         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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155121#comment-155121 ]

Andrew Martignoni III commented on JENKINS-11073:
-------------------------------------------------

I also rolled back to Copy Aritifact 1.16 to fix the problem.  I'm running with 1.433 on a Win XP master with a Win XP slave.
               

> 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: Kohsuke Kawaguchi
>         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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155272#comment-155272 ]

dan russell commented on JENKINS-11073:
---------------------------------------

Unfortunately I'm using copy artifact with matrix jobs and join plugin, so I'm unable to revert to 1.16 and  stuck at jenkins 1.424
               

> 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: Kohsuke Kawaguchi
>         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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155307#comment-155307 ]

j f commented on JENKINS-11073:
-------------------------------

Yeah rolling back should only be a temporary solution. And I really hope this is getting fixed within the next month. Please vote for this bug to get fixed.
               

> 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: Kohsuke Kawaguchi
>         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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155339#comment-155339 ]

kutzi commented on JENKINS-11073:
---------------------------------

How are you connecting the windows slaves? Have you checked that the slaves have the latest version of the slave.jar?
               

> 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: Kohsuke Kawaguchi
>         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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155354#comment-155354 ]

kutzi commented on JENKINS-11073:
---------------------------------

According to the comments here http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4243868 problems with setLastModified seems to be a widespread problem on Windows platforms
               

> 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: Kohsuke Kawaguchi
>         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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155355#comment-155355 ]

scm_issue_link commented on JENKINS-11073:
------------------------------------------

Code changed in jenkins
User: Christoph Kutzinski
Path:
 core/src/main/java/hudson/FilePath.java
http://jenkins-ci.org/commit/jenkins/a7ce870c1ad1a7ff67962ecfc9830949d9e2861d
Log:
  [FIXED JENKINS-11073] handle failure to set timestamp on Windows platforms more gracefully




               

> 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: Kohsuke Kawaguchi
>         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

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

scm_issue_link resolved JENKINS-11073.
--------------------------------------

    Resolution: Fixed
   

> 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: Kohsuke Kawaguchi
>         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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155356#comment-155356 ]

dogfood commented on JENKINS-11073:
-----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1282|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1282/]
     [FIXED JENKINS-11073] handle failure to set timestamp on Windows platforms more gracefully

Christoph Kutzinski : [a7ce870c1ad1a7ff67962ecfc9830949d9e2861d|https://github.com/jenkinsci/jenkins/commit/a7ce870c1ad1a7ff67962ecfc9830949d9e2861d]
Files :
* core/src/main/java/hudson/FilePath.java

               

> 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: Kohsuke Kawaguchi
>         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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155369#comment-155369 ]

scm_issue_link commented on JENKINS-11073:
------------------------------------------

Code changed in jenkins
User: Christoph Kutzinski
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/4dc4678fd85c790fb619acb6e3c1cea7181863ce
Log:
  Changelog for JENKINS-8383 and JENKINS-11073


Compare: https://github.com/jenkinsci/jenkins/compare/a7ce870...4dc4678


               

> 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: Kohsuke Kawaguchi
>         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

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dan russell reopened JENKINS-11073:
-----------------------------------


Jenkins 1.440 with copy artifact 1.18

ERROR: Failed to copy artifacts from 3.8-distribution with filter: distribution-zip/target/distribution.zip
hudson.util.IOException2: remote file operation failed: c:\app\hudson\workspace\3.8-jelly-db\jdk/jdk1.6.0_21/label/sqlserver/profile/sqlserver\acceptance-tests\distribution.zip at hudson.remoting.Channel@1122fc6:tal-bri-tate-8
        at hudson.FilePath.copyToWithPermission(FilePath.java:1435)
        at hudson.plugins.copyartifact.FilePathCopyMethod.copyOne(FilePathCopyMethod.java:58)
        at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:231)
        at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:186)
        at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
        at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692)
        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:462)
        at hudson.model.Run.run(Run.java:1404)
        at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
        at hudson.model.ResourceController.execute(ResourceController.java:88)
        at hudson.model.Executor.run(Executor.java:230)
Caused by: hudson.util.IOException2: remote file operation failed: c:\app\hudson\workspace\3.8-jelly-db\jdk/jdk1.6.0_21/label/sqlserver/profile/sqlserver\acceptance-tests\distribution.zip at hudson.remoting.Channel@1122fc6:tal-bri-tate-8
        at hudson.FilePath.act(FilePath.java:779)
        at hudson.FilePath.act(FilePath.java:765)
        at hudson.FilePath.touch(FilePath.java:1061)
        at hudson.FilePath.copyToWithPermission(FilePath.java:1429)
        ... 12 more
Caused by: java.io.IOException: Failed to set the timestamp of c:\app\hudson\workspace\3.8-jelly-db\jdk\jdk1.6.0_21\label\sqlserver\profile\sqlserver\acceptance-tests\distribution.zip to 1321879253000
        at hudson.FilePath$17.invoke(FilePath.java:1066)
        at hudson.FilePath$17.invoke(FilePath.java:1061)
        at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2030)
        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 java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        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 'Copy artifacts from another project' 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: Kohsuke Kawaguchi
>         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