'Access violation in the error log' is probably JENKINS-20630 / JENKINS-20779.
On 03.12.2013, at 22:53, Mark Waite <[email protected]> wrote: > That is good to hear. If you can afford the time, I think the developers > would like to know you're setup that failed upgrade. However, they need you > to narrow the cause of the upgrade failure and that usually takes time and > experimentation > > Mark > > On Dec 3, 2013 12:22 PM, "Mark Mikulec" <[email protected]> wrote: > Hi Mark, > > Thanks for the tip - that build worked flawlessly! > > Mark > > __________________________________________________ > Learn more about.me. > > > On 2 December 2013 13:48, Mark Waite <[email protected]> wrote: > If you were running a version of Jenkins for that long without upgrading, you > might also consider upgrading to the Long Term Support version instead of > upgrading to the latest tip of development. The long term support version is > currently 1.532.1 and is available from > http://mirrors.jenkins-ci.org/war-stable/1.532.1/. > > Mark Waite > > > On Mon, Dec 2, 2013 at 11:40 AM, Walter Kacynski <[email protected]> > wrote: > 1.) All builds are cumulative so you just need to pick the version that you > want to run. > > Please share the error message that you are seeing. Also, did you try > searching http://issues.jenkins-ci.org for your error message? > > > On Monday, December 2, 2013 12:54:55 PM UTC-5, bluntcoder wrote: > Hello, > > I'm trying to upgrade my fully functional Jenkins build (v1.472) to the > latest version on Windows XP. The automatic update failed. I tried doing a > manual update, it also failed. It is due to an access violation in the > jenkins.err.log on bootup. One thing I tried was adding in JENKINS_HOME > manually, since it wasn't present. However that did not fix it. I ended up > reverting to the old build for now. > > At this point I wouldn't be surprised if my build is just too old to do in > place update, so I'm wondering what's the best approach here: > > Do I: > 1) Upgrade the war file manually, which would be very tedious, since there's > 69 versions in between, or perhaps I could get a list of which wars I can > skip to ensure any configuration changes required are taken care of? > or > 2) Install a totally new build of Jenkins on the same machine, and then > somehow transfer my configuration settings over to the new build, and kill > the old one. > or something else suggested by someone on this forum. > > Any input is greatly appreciated. > > Thanks! > Mark > > > > > > > -- > 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 [email protected]. > > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/r11r4sT2d4s/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
