Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Deployed files have incorrect time stamp
-
I'm not sure how long this is going on as I had not noticed it and someone else brought it my attention.
First let me say that the all of the machines involved are on the same time zone.I grab an artifact from Jenkins, create a BM artifact and then it gets deployed.
The BM artifact, if I download it and examine it, has the correct time stamps.
When the files are deployed to the server they end up with a different timestamp, same date but way off on the time. For example I did on that the time stamp for the files should be 325pm but on the machine it is deployed to it is 825am.
The files are the correct versions so it's just a confusing thing to people.Product: BuildMaster
Version: 5.6.11
-
This is a known issue (BM-3040), with the problem being there's no standard way to store timezone offsets in a .zip file. BuildMaster assumes all timestamps in an artifact are UTC by convention, so on deployment the file times are set assuming the timestamp in the artifact is UTC. Jenkins must store their zip files in local time, so there's a double-conversion happening.
We have had a few discussions about this issue and it applies to TeamCity and TFS as well. We can either store custom metadata in the .zip somehow, or the easiest solution would probably be another property on the Deploy Artifact operation that specifies the source timezone offset.
-
Another option to consider is just defaulting to the BuildMaster Server time zone.
At least for us that is the same as the Jenkins system.
So use that as a Default but allow a setting in the Artifact Deployer if someone needs to be different.