Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11073

copy artifact fails on windows XP slaves due to failing to set a timestamp

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • copyartifact-plugin, core
    • 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

          [JENKINS-11073] copy artifact fails on windows XP slaves due to failing to set a timestamp

          Jeff Koenig created issue -

          Alan Harder added a comment -

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

          Alan Harder added a comment - 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..
          Alan Harder made changes -
          Assignee Original: Alan Harder [ mindless ] New: Kohsuke Kawaguchi [ kohsuke ]

          b2jrock added a comment -

          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.

          b2jrock added a comment - 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.

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

          Conny Kreyßel added a comment - Same here, we rolled back to jenkins 1.427 and all works fine.

          j f added a comment - - edited

          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)

          j f added a comment - - edited 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)

          dan russell added a comment -

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

          dan russell added a comment - Just tried to upgrade from 1.424 to 1.432 and experienced this issue

          Luke Last added a comment -

          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.

          Luke Last added a comment - 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.

          j f added a comment -

          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/)

          j f added a comment - 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/ )
          dan russell made changes -
          Link New: This issue is related to JENKINS-10805 [ JENKINS-10805 ]

            kohsuke Kohsuke Kawaguchi
            jkoenig Jeff Koenig
            Votes:
            20 Vote for this issue
            Watchers:
            25 Start watching this issue

              Created:
              Updated:
              Resolved: