Quantcast

Jenkins showing wrong time-stamps for all Builds

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Jenkins showing wrong time-stamps for all Builds

krishna chaitanya kurnala
Hello Everyone

For some reason, all the times of builds of our Jenkins are in Universal Timezone while we are Pacific Time Zone(LA) 
user.timezone = Universal

did anyone face the same problem earlier? How did you fix it though ? 

Thanks,
Krishna Chaitanya
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Jenkins showing wrong time-stamps for all Builds

Sami Tikka
No, I have to faced the same problem.

You might get better help if you gave some more details about your system:

What is your operating system? If the clock of your OS correct? Is the time zone of your OS correct?

How did you install Jenkins? Which version?

-- Sami

krishna chaitanya kurnala <[hidden email]> kirjoitti 26.7.2012 kello 20.06:

> Hello Everyone
>
> For some reason, all the times of builds of our Jenkins are in Universal Timezone while we are Pacific Time Zone(LA)
> user.timezone = Universal
>
> did anyone face the same problem earlier? How did you fix it though ?
>
> Thanks,
> Krishna Chaitanya
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Jenkins showing wrong time-stamps for all Builds

krishna chaitanya kurnala
Hi Sami

Here are the details you requested: 

[jenkinspan@sdc-cidev10 ~]$ date
Thu Jul 26 15:31:05 PDT 2012
[jenkinspan@sdc-cidev10 ~]$ uname -a
Linux sdc-cidev10 2.6.18-238.12.1.el5 #1 SMP Sat May 7 20:18:50 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

Jenkins version: 1.474 (almost latest). I am deploying jenkins.war in Tomcat.

This is Strange, dont know how to solve. Appreciate some help.

Thanks
Krishna Chaitanya


On Thu, Jul 26, 2012 at 11:47 AM, Sami Tikka <[hidden email]> wrote:
No, I have to faced the same problem.

You might get better help if you gave some more details about your system:

What is your operating system? If the clock of your OS correct? Is the time zone of your OS correct?

How did you install Jenkins? Which version?

-- Sami

krishna chaitanya kurnala <[hidden email]> kirjoitti 26.7.2012 kello 20.06:

> Hello Everyone
>
> For some reason, all the times of builds of our Jenkins are in Universal Timezone while we are Pacific Time Zone(LA)
> user.timezone = Universal
>
> did anyone face the same problem earlier? How did you fix it though ?
>
> Thanks,
> Krishna Chaitanya

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Jenkins showing wrong time-stamps for all Builds

Sami Tikka
Then the timezone of the JVM comes from whatever tomcat decides or the script that starts tomcat. It doesn't look like it is a Jenkins problem. 

Have you checked System Information under Manage Jenkins page? Does it show something about the time zone? A property? Or an environment variable?

-- Sami

krishna chaitanya kurnala <[hidden email]> kirjoitti 27.7.2012 kello 1.35:

Hi Sami

Here are the details you requested: 

[jenkinspan@sdc-cidev10 ~]$ date
Thu Jul 26 15:31:05 PDT 2012
[jenkinspan@sdc-cidev10 ~]$ uname -a
Linux sdc-cidev10 2.6.18-238.12.1.el5 #1 SMP Sat May 7 20:18:50 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

Jenkins version: 1.474 (almost latest). I am deploying jenkins.war in Tomcat.

This is Strange, dont know how to solve. Appreciate some help.

Thanks
Krishna Chaitanya


On Thu, Jul 26, 2012 at 11:47 AM, Sami Tikka <[hidden email]> wrote:
No, I have to faced the same problem.

You might get better help if you gave some more details about your system:

What is your operating system? If the clock of your OS correct? Is the time zone of your OS correct?

How did you install Jenkins? Which version?

-- Sami

krishna chaitanya kurnala <[hidden email]> kirjoitti 26.7.2012 kello 20.06:

> Hello Everyone
>
> For some reason, all the times of builds of our Jenkins are in Universal Timezone while we are Pacific Time Zone(LA)
> user.timezone = Universal
>
> did anyone face the same problem earlier? How did you fix it though ?
>
> Thanks,
> Krishna Chaitanya

Loading...