[
https://issues.jenkins-ci.org/browse/JENKINS-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johannes Schmieder updated JENKINS-7228:
----------------------------------------
Seems to be solved by JENKINS-13122.
> Archiving artifacts does not preserve timestamps
> ------------------------------------------------
>
> Key: JENKINS-7228
> URL: https://issues.jenkins-ci.org/browse/JENKINS-7228
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Windows Server 2003, .NET development
> Reporter: joshglg
>
> We rely on date/time-stamps to deploy only the code that has changed to our
> various environments. While developing a deployment mechanism to deploy from
> the archived Hudson artifacts for a particular build, we realized that upon
> archival of the artifacts, Hudson sets the timestamps of all archived files
> to the present time (when the archiving is taking place). This is preventing
> us from deploying only the code that has changed.
> Shouldn't Hudson preserve the timestamps when it is archiving the artifacts?
--
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
