-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Server: Windows Server 2008 R2, Tomcat 6.0.20, JDK 1.6.0_20, Hudson 1.357
Client: Windows 7 Enterprise, Google Chrome 5.0
When viewing a job, the timeline displays times using GMT rather than the server's timezone — EDT (GMT-0400) in my case. This means that a build which took place at 12:57 PM shows up right before "17h" on the timeline, but it should appear right before "13h" (see attached screenshot).
- is related to
-
JENKINS-49626 Wrong timestamps in build timeline (twice GMT shift it seems)
-
- Open
-
-
JENKINS-10184 wrong timestamps in build timeline
-
- Resolved
-
[JENKINS-6692] Timeline should use server's timezone, not GMT
Assignee | New: Alan Harder [ mindless ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Verified [ 10000 ] |
Status | Original: Verified [ 10000 ] | New: Reopened [ 4 ] |
Attachment | New: JENKINS-6692.png [ 20645 ] |
Code changed in hudson
User: : mindless
Path:
trunk/hudson/main/core/src/main/resources/hudson/model/Job/buildTimeTrend.jelly
trunk/www/changelog.html
http://jenkins-ci.org/commit/31945
Log:
[FIXED JENKINS-6692] Timeline on build trend page should use server timezone
instead of always GMT.