You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This took me some time to find out.
My timezone - PDT - is UTC-7
So if I start a build and it fails after 5pm, the date will change...
That happens very often in the US West coast.
there should be a better strategy for this.
The text was updated successfully, but these errors were encountered:
In build.sh, line 131, it assigns the IMG_DATE variable to the current UTC date if the IMG_DATE variable is not set. You should be able to invoke the script using: IMG_DATE=`date +%Y-%m-%d` ./build.sh if you want to set your own date. However, this won't work with the Docker build script (the docker container will be using UTC), you will have to set IMG_DATE in your config file prior to running it.
That said, I don't like the fact that the date is UTC either. I propose we change it to always use the local system timezone. It can always be overridden using the IMG_DATE variable.
Also, it's minor, but the title of a bug should state what is happening (what problem you are observing), not what the solution is. E.g. "The build date is always UTC, even with different time zone settings" or "The build date does not honour the local timezone", or something like that
g-e-r
changed the title
should not use UTC time as build date
The build date is always UTC, even with different time zone settings
Jun 2, 2017
This took me some time to find out.
My timezone - PDT - is UTC-7
So if I start a build and it fails after 5pm, the date will change...
That happens very often in the US West coast.
there should be a better strategy for this.
The text was updated successfully, but these errors were encountered: