if you view a build that was built when in a DST offset when not currently in a DST offset the timestamp time (when using use "Use browser timezone") is off by one.
the same is true if the inverse occurs (a build was done when not in a DST offset and you are currently in DST offset).
The time printed when using the local timezone should be the actual time that it took place in the local timezone according to any DST rules that are in place at the time.
E.g. with browser set to Europe/London (currently no DST offset so UTC+1) view
https://weekly.ci.jenkins.io/job/pipeline/3/console (note this build was started Build #3 (7 Jul 2023, 16:30:06 BST , aka 7 Jul 2023, 15:30:06 UTC)
Note the timestamps are showing `15:30:06` in the console whereas the local time is infact 16:30:06 .
changing to use a zone that has a larger starndard offset from UTC will show the miscalulation more pronounced.
Originally reported by 
teilo, imported from: timezone offset ignores DST in builds
- status: Open
- priority: Minor
- component(s): timestamper-plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20251218-075729
Raw content of original issue
if you view a build that was built when in a DST offset when not currently in a DST offset the timestamp time (when using use "Use browser timezone") is off by one.
the same is true if the inverse occurs (a build was done when not in a DST offset and you are currently in DST offset).
The time printed when using the local timezone should be the actual time that it took place in the local timezone according to any DST rules that are in place at the time.
E.g. with browser set to Europe/London (currently no DST offset so UTC+1) view
https://weekly.ci.jenkins.io/job/pipeline/3/console (note this build was started Build #3 (7 Jul 2023, 16:30:06 BST , aka 7 Jul 2023, 15:30:06 UTC)
Note the timestamps are showing `15:30:06` in the console whereas the local time is infact 16:30:06 .
changing to use a zone that has a larger starndard offset from UTC will show the miscalulation more pronounced.
if you view a build that was built when in a DST offset when not currently in a DST offset the timestamp time (when using use "Use browser timezone") is off by one.
the same is true if the inverse occurs (a build was done when not in a DST offset and you are currently in DST offset).
The time printed when using the local timezone should be the actual time that it took place in the local timezone according to any DST rules that are in place at the time.
E.g. with browser set to Europe/London (currently no DST offset so UTC+1) view
https://weekly.ci.jenkins.io/job/pipeline/3/console (note this build was started Build #3 (7 Jul 2023, 16:30:06 BST , aka 7 Jul 2023, 15:30:06 UTC)
Note the timestamps are showing `15:30:06` in the console whereas the local time is infact 16:30:06 .
changing to use a zone that has a larger starndard offset from UTC will show the miscalulation more pronounced.
Originally reported by
teilo, imported from: timezone offset ignores DST in builds
Raw content of original issue