Re: Build date / time showing December 31, 1969 after upgrading from 1.596.2 LTS to 1.625.3

2015-12-23 Thread Marc Esher 
OK, I now see what's going on specifically in my case. Definitely one of 
those stupid problems that I imagine there's no way Jenkins could account 
for it, so if I really care about fixing it I think I need to script a 
solution.

Here's the deal: it's all related to the build format migration that 
happened between 1.596 and 
1.597: https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration, 
in combination with a system that's partially managed by puppet, and 
partially not.

The root cause of the builds in question showing the epoch is that their 
build.xml does not have a  element.

In our case, the reason is this: during a normal patch cycle, jenkins was 
yum-updated to a newer version, and the migration described in that wiki 
page happened correctly. Then, sometime after, puppet ran, and our puppet 
at that time was configured to pin jenkins to 1.596, and so it downgraded 
jenkins. This cycle probably repeated one or two times (we simply didn't 
realize it).

And so now, in each job's builds directory, we have a mix of old and new 
format build.xml files. All the symlinks are correct, but the busted builds 
do not have a  element.

It's good to at least know exactly what happened.

Marc

On Wednesday, December 23, 2015 at 1:23:26 AM UTC-5, Baptiste Mathus wrote:
>
> Just a small hint, in case it can help get you forward: the date you have 
> seems to match Epoch. 
> So I suppose at some point, the computed timestamp for the build is 0 (or 
> defaulted to).
>
> My 0.2 cents.
>
> 2015-12-22 22:32 GMT+01:00 Marc Esher >:
>
>> Hey Steve, 
>>
>> I did not resolve this problem on 2 of the jenkinses. However, on a 3rd, 
>> I did a straight update from 1.596 to 1.625, and I did not experience this 
>> behavior, so I'm thinking that my original problem is not quite as 
>> described. It seems that the problem originated on the busted jenkinses in 
>> question during a previous update, from 1.596 to some other version, 
>> presumably in the 1.6 + range, but I'm just not sure. 
>>
>> On those busted servers, I have not figured out how to resolve the 
>> problem. The symlinks are all in tact, but Jenkins can't seem to figure out 
>> what to make of them.
>>
>> Sorry I can't be more helpful.
>>
>> On Tuesday, December 22, 2015 at 3:14:14 PM UTC-5, Steve K wrote:
>>>
>>>
>>> Marc,
>>>
>>> Did you ever resolve your problem?  I have a feeling that my current 
>>> upgrade HELL (just posted a plea for help on that) is related to changes in 
>>> format.
>>> If you haven't resolved it, sorry if I got your hopes up when you saw a 
>>> reply :-(
>>>
>>> Regards,
>>>
>>> Steve K.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/9bed974c-fec2-4c14-b883-0940228ea411%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ae4f6ceb-3f68-4508-9132-ea0f20a21c56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build date / time showing December 31, 1969 after upgrading from 1.596.2 LTS to 1.625.3

2015-12-22 Thread Baptiste Mathus 
Just a small hint, in case it can help get you forward: the date you have
seems to match Epoch.
So I suppose at some point, the computed timestamp for the build is 0 (or
defaulted to).

My 0.2 cents.

2015-12-22 22:32 GMT+01:00 Marc Esher :

> Hey Steve,
>
> I did not resolve this problem on 2 of the jenkinses. However, on a 3rd, I
> did a straight update from 1.596 to 1.625, and I did not experience this
> behavior, so I'm thinking that my original problem is not quite as
> described. It seems that the problem originated on the busted jenkinses in
> question during a previous update, from 1.596 to some other version,
> presumably in the 1.6 + range, but I'm just not sure.
>
> On those busted servers, I have not figured out how to resolve the
> problem. The symlinks are all in tact, but Jenkins can't seem to figure out
> what to make of them.
>
> Sorry I can't be more helpful.
>
> On Tuesday, December 22, 2015 at 3:14:14 PM UTC-5, Steve K wrote:
>>
>>
>> Marc,
>>
>> Did you ever resolve your problem?  I have a feeling that my current
>> upgrade HELL (just posted a plea for help on that) is related to changes in
>> format.
>> If you haven't resolved it, sorry if I got your hopes up when you saw a
>> reply :-(
>>
>> Regards,
>>
>> Steve K.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/9bed974c-fec2-4c14-b883-0940228ea411%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4ERWBTQamisSM2_PAbE_hRTMYEF1oojyTsSFrH8LbYbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build date / time showing December 31, 1969 after upgrading from 1.596.2 LTS to 1.625.3

2015-12-22 Thread Marc Esher 
Hey Steve, 

I did not resolve this problem on 2 of the jenkinses. However, on a 3rd, I 
did a straight update from 1.596 to 1.625, and I did not experience this 
behavior, so I'm thinking that my original problem is not quite as 
described. It seems that the problem originated on the busted jenkinses in 
question during a previous update, from 1.596 to some other version, 
presumably in the 1.6 + range, but I'm just not sure. 

On those busted servers, I have not figured out how to resolve the problem. 
The symlinks are all in tact, but Jenkins can't seem to figure out what to 
make of them.

Sorry I can't be more helpful.

On Tuesday, December 22, 2015 at 3:14:14 PM UTC-5, Steve K wrote:
>
>
> Marc,
>
> Did you ever resolve your problem?  I have a feeling that my current 
> upgrade HELL (just posted a plea for help on that) is related to changes in 
> format.
> If you haven't resolved it, sorry if I got your hopes up when you saw a 
> reply :-(
>
> Regards,
>
> Steve K.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9bed974c-fec2-4c14-b883-0940228ea411%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build date / time showing December 31, 1969 after upgrading from 1.596.2 LTS to 1.625.3

2015-12-22 Thread Steve K 

Marc,

Did you ever resolve your problem?  I have a feeling that my current 
upgrade HELL (just posted a plea for help on that) is related to changes in 
format.
If you haven't resolved it, sorry if I got your hopes up when you saw a 
reply :-(

Regards,

Steve K.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/46102b90-ced0-42a6-97b1-802731709182%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Build date / time showing December 31, 1969 after upgrading from 1.596.2 LTS to 1.625.3

2015-12-21 Thread Marc Esher 
Greetings all.

After upgrading from 1.596.2 LTS to 1.625.3 LTS, all my jobs are showing 
"Dec 31, 1969" as the build date in the build history.

It appears the reason is that Jenkins has switched from using a 
date/time-based directory in "builds" to a simple number-based directory, 
but even though the symlinks are correct, something appears to be causing 
Jenkins to no longer be able to understand what's what.

If I drill into one of these builds in the UI, it does have a lot of data: 
git revisions, env variables, console output, so it can at least read 
something about these builds... but the date/time is wrong.

Any advice for fixing this?

Thanks! 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e131b779-1d88-46ea-b968-dd71c84e81a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.