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
What steps will reproduce the problem?
1. I'm running GitBlit on a server with UTC time zone
2. I'm launching GitBlit using tomcat and setting Java's time zone to using -Duser.timezone=Americas/Los_Angeles
3. I modified web.xml and appended "z" to all the time/date formats to see the time
zones
4. The dates on the commit log are correct and are shown as PST, but the date/times
on the main "Activity" tab are all in GMT.
What is the expected output? What do you see instead?
The dates on the activity tab should be PST
What version of the product are you using? On what operating system?
0.8.2 WAR on Tomcat 6.0.
Please provide any additional information below.
I think the best would be to have a setting in GitBlit to set the time zone. This way,
I can set the JVM time zone to UTC too so my logs would be in UTC. In addition, since
the actual git blob files are being created using the UTC times this makes things simpler.
Reported by Drew.Kutcharian on 2012-02-03 02:10:15
The text was updated successfully, but these errors were encountered:
Gitblit uses the server's timezone unless you are allowing browser timezone identification
web.useClientTimezone. I'm not sure why the activity page would be different since
it should be using the same date formatting as everything else. I'll consider adding
a Gitblit timezone setting, but since it can be overridden with a -D parameter it seems
unnecessary.
I configured my timestamps as you did and then used the exact parameter you specified.
My activity dates were in GMT as you indicated they would be... but so were all other
dates.
There is a typo in your parameter: "America/Los_Angeles" is the correct value. When
I run it using the correct timezone the activity page shows all dates/times as PST
as does the rest of Gitblit.
Originally reported on Google Code with ID 54
Reported by
Drew.Kutcharian
on 2012-02-03 02:10:15The text was updated successfully, but these errors were encountered: