cachebuster type timestamp is using local time

[lukasriederle]

Expected Behavior

timestamp for cachebuster should be generated in a central timezone

Current Behavior

timestamp is written in local timezone and therefore leads to an error:
time stamp 2019-07-25 16:25:14 is 5221.004068479 s in the future when starting soon.

Steps to reproduce the issue

1. generate app in e.g. German Timezone. then run it imediately on a server with time difference.

Log Output / Stack Trace

[PollStageAppStatusExecution]  8be308c5-b2a9-4a43-ab9d-01f76fd1529e [Tue Jul 29 09:43:32 UTC 49565270] Copying droplet into the container failed: stream-in: nstar: error streaming in: exit status 2. Output: tar: ./app/public/Component-dbg.js: time stamp 2019-07-25 16:25:14 is 5221.004068479 s in the future (STDERR, CELL)#

[RandomByte]

Related: SAP/ui5-builder#294 (comment) actually not related

[matz3]

The task uses getTime() on the modified date of the file, which returns the milliseconds since Jan 1 1970 UTC, so it should not differ depending on the timezone
https://github.com/SAP/ui5-builder/blob/9b5498a254ed7d1b008c640d01981861dc25bbd4/lib/tasks/generateCachebusterInfo.js#L5

Maybe the server-side part is interpreting the UTC time with its local time?
At least I can not see where this could be solved in the builder/task, thus closing this issue.