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.
