-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
German Translation
Windows Server 2008 R2 Standard
Tomcat 7.0.16
Time Zone UTC+1
The timestamps shown in the build timeline differ from the actual time of the builds by -1 hour. The machine is based in time zone utc+1. See the attached screenshot for further information.
- is duplicated by
-
JENKINS-13899 Build History timeline is off by an hour (daylight savings issue?)
-
- Resolved
-
- is related to
-
JENKINS-6692 Timeline should use server's timezone, not GMT
-
- Reopened
-
-
JENKINS-49626 Wrong timestamps in build timeline (twice GMT shift it seems)
-
- Open
-
I also reproduce the issue with Jenkins 1.440.
In /systeminfo, I have user.timezone = Europe/Paris (UTC+1).
In the build history, there is a build at "14:36:22" (in June) but in the timeline, the same build is displayed at "13:36:22" as shown in the tooltip (BAD).
And also, in the build history, there is another build at "15:21:25" (in January) and in the timeline, the same build is displayed at "15:21:25" as shown in the tooltip (GOOD).
So it seems to be an issue of daylight saving time, and in the same timeline some builds are bad and others are good.
In [1], I see that java.util.TimeZone.getDefault().getRawOffset() is used.
Perhaps, java.util.TimeZone.getDefault().getOffset(date.getTime()) should be used instead for each date, or the timezone of the dates could be changed on the server before sending the JSON of the timeline data to the client.
[1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/BuildTimelineWidget/control.jelly#L42