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 tha
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
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 jenkin
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 be
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 thou
