[JIRA] [core] (JENKINS-23645) Archiving artifacts does not preserve timestamps if archived on master

Tue, 12 Aug 2014 16:23:27 -0700

That's exactly what @danielbeck pointed.
Thanks for clarifying.
I updated the summary and the description.

I think it won't be fixed so soon, and you'd better try workarounds like:

  • Archive files with zip command in the upstream project, and extract them with unzip in the downstream project.
  • Have builds run only on slaves. This can be done by enabling "Restrict where this project can be run" in project configuration pages.
Change By: ikedam (12/Aug/14 11:21 PM)
Summary: Archiving artifacts does not preserve timestamps if  filter is **  archived on master
Assignee: Gregory Boissinot
Environment: Windows 7 , Java 1.8, Jenkins 1.575
Description: When a build run on the master, "Archive the artifacts" doesn't preserve timestamps.
It preserves timestamps when run on slaves.

It looks caused by {{FilePath.copyRecursiveTo}}.

----
Original description (the issue was found not of Copyartifact,  but of ArtifactArchiver):

 The timestamps of artifacts are not preserved when archiving artifacts, OR performing a CopyArtifact operation if the artifact filter is set to "**".

For example the filter {code}"myfolder\**"{code} will preserve timestamps.

We use mutiple chained Jenkins jobs to perform a build. If the timestamps of dependency files in the artifact passed between jobs is not preserved, then subsequent jobs will fail.
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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to