|
||||||||||||||
|
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.
I ran into the same problem.
The timestamp of all the archived artifacts is reset to the time and date they were archived.
The problem is easy to spot. Check this directory (or the equivalent on your setup):
C:\Jenkins\jobs\MyJob\builds\2014-07-01_01-01-01\archive
Note that the date and time of all files in this folder has been set to the time when they were archived.
I am trying to setup a multi-stage HDL build pipeline, where one job compiles the project, and another job performs layout.
I use CopyArtifacts to transfer the artifacts from the first to the second job.
But because the timestamp on all files are changed by jenkins, the second job detects that dependencies have changed and assumes that the project is in a pre-compile state. So it refuses to run the layout step.
The cited "
JENKINS-13122" only solves this problem for the ZIP-version of artifact archiving. The problem still remains for regular uncompressed artifacts.I cannot use compressed artifacts as a workaround, since I am using CopyArtifacts. The two are not compatible.
(We are using Jenkins 1.565)