Upgrade from 1.472 to 1.541 failing

[bluntcoder]

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

[Walter Kacynski]

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?

[Mark Waite]

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

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Mark Mikulec]

Hi Mark,

Thanks for the tip - that build worked flawlessly!

Mark

__________________________________________________

Learn more about.me.

--
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 jenkinsci-use...@googlegroups.com.

[Mark Waite]

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

[Daniel Beck]

'Access violation in the error log' is probably JENKINS-20630 / JENKINS-20779.

[Mark Mikulec]

Confirmed,

JENKINS-20630.