Currently it seems that the modification dates of all files in artifacts are reset to 1970-01-01T00:00:00Z (Unix time 0). Here's an example artifact for instance.
It seems that the archives are created using something like
tar --owner=root:0 --group=root:0 --mtime='UTC 1970-01-01'
This causes side-effects downstream, which I can't really blame Bitbucket on though, e.g. Adobe Reader loading outdated cache. I'm not sure what the motivation behind is but for me it'd be nice to have a straightforward approach to tackle this.
PS: I've found a Bamboo issue that looks rather similar https://community.atlassian.com/t5/Bamboo-questions/Keep-original-timestamp-on-build-artifacts-during-artifact/qaq-p/295379
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events