Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-15161] Dashboard views use system time instead of Jenkins time #233

Closed
TobiX opened this issue Sep 13, 2012 · 3 comments · Fixed by #328
Closed

[JENKINS-15161] Dashboard views use system time instead of Jenkins time #233

TobiX opened this issue Sep 13, 2012 · 3 comments · Fixed by #328

Comments

@TobiX
Copy link
Contributor

TobiX commented Sep 13, 2012

I'm using the Dashboard View plugin and using the "latest builds" view. The system that Jenkins runs on has its clock set to UTC, but I have the Jenkins timezone set to PST. On all the native Jenkins pages, such as job build history, I see timestamps in PST. In the "latest builds" view the times are all UTC.

I set the timezone for Jenkins by running it like this on the command line: java -Dorg.apache.commons.jelly.tags.fmt.timeZone=America/Los_Angeles -jar jenkins.war


Originally reported by owenmehegan, imported from: Dashboard views use system time instead of Jenkins time
  • status: Open
  • priority: Major
  • resolution: Unresolved
  • imported: 2022-10-30
@TobiX
Copy link
Contributor Author

TobiX commented Mar 21, 2013

mkruer:

It would be nice if the dashboard was able to detect the user time zone thought the browser and show the times local regardless of what the settings are. This make people viewing the dashboard internationally not have to mentally calculate what time a job kicks off and would be very helpfully for automatic deployment.

@TobiX
Copy link
Contributor Author

TobiX commented Oct 11, 2013

owenmehegan:

Marco - I noticed you have done work on this plugin recently. Any thoughts on this issue? It is still present in the latest version.

@TobiX
Copy link
Contributor Author

TobiX commented Aug 19, 2018

tgr:

I suspect even if the ticket is very old, the issue still exists?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant