Upgrading from v1.652 to v2.50

[Anca Cimpoaca]

Hello,

 

I'm trying to upgrading our Jenkins currently on version v1.652, installed as a service on Windows Server 2012 R2.

 

When trying to upgrade automatically to the latest v2.50, we followed these steps:

Jenkins.war.tmp (67,285K) gets downloaded. The size seems correct.

 

Then I click "restart" as in the screenshot below:

 

At this point, it Jenkins is still on v1.652.  Jenkins.out.log logs some warnings, as below:

Mar 17, 2017 6:55:10 PM hudson.model.UpdateCenter doUpgrade
INFO: Scheduling the core upgrade
Mar 17, 2017 6:55:10 PM hudson.model.UpdateCenter$DownloadJob run
INFO: Starting the installation of jenkins.war on behalf of anonymous
Mar 17, 2017 6:55:10 PM hudson.model.UpdateCenter$UpdateCenterConfiguration download
INFO: Downloading jenkins.war
Mar 17, 2017 6:55:19 PM hudson.model.UpdateCenter$DownloadJob run
INFO: Installation successful: jenkins.war
Mar 17, 2017 6:55:49 PM jenkins.model.Jenkins$25 run
INFO: Restart in 10 seconds
Mar 17, 2017 6:55:59 PM jenkins.model.Jenkins$25 run
SEVERE: Restarting VM as requested by anonymous
Mar 17, 2017 6:56:01 PM winstone.Logger logInternal
INFO: Beginning extraction from war file
Mar 17, 2017 6:56:01 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-winstone-2.9
Mar 17, 2017 6:56:02 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet
Mar 17, 2017 6:56:02 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started SelectChann...@0.0.0.0:9292
Mar 17, 2017 6:56:02 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
Mar 17, 2017 6:56:02 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Mar 17, 2017 6:56:02 PM hudson.ClassicPluginStrategy createPluginWrapper
INFO: Plugin clearcase-ucm-plugin.jpi is disabled
Mar 17, 2017 6:56:03 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Mar 17, 2017 6:56:03 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Mar 17, 2017 6:56:06 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Mar 17, 2017 6:56:06 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Mar 17, 2017 6:56:09 PM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Mar 17, 2017 6:56:09 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Download metadata
Mar 17, 2017 6:56:09 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Download metadata. 0 ms
Mar 17, 2017 6:56:09 PM org.jenkinsci.main.modules.sshd.SSHD start
INFO: Started SSHD at port 49502
Mar 17, 2017 6:56:09 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Mar 17, 2017 6:56:09 PM jenkins.model.Jenkins <init>
INFO: Installing chromedriver to C:\jenkins\home\tools\chromedriver
Mar 17, 2017 6:56:09 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Mar 17, 2017 6:56:09 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Mar 17, 2017 6:56:09 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Mar 17, 2017 6:56:09 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Mar 17, 2017 6:56:09 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Mar 17, 2017 6:56:09 PM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Mar 17, 2017 6:56:09 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Mar 17, 2017 6:56:09 PM hudson.WebAppMain$3 run
INFO: Jenkins is fully up and running
Mar 17, 2017 6:56:15 PM jenkins.model.PeepholePermalink updateCache
WARNING: Failed to update hudson.model.FreeStyleProject@33352f71[CI Revamp - Front-End] lastSuccessfulBuild permalink for CI Revamp - Front-End #80
java.nio.file.DirectoryNotEmptyException: C:\jenkins\home\jobs\CI FrontEnd\builds\lastSuccessfulBuild
    at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
    at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source)
    at java.nio.file.Files.delete(Unknown Source)
 ...............................

 

Can someone please advice ? A couple of weeks ago, I managed to upgrade from v1.652 to v2.48 on a different server, with another Jenkins instance.

 

If we download the war v2.50 manually and replace the jenkins.war, what would be the implications ? Can I safely revert if something goes wrong ? Is it worth trying updating to v2.48 that worked but in a different Jenkins instance ?

 

Thank you!

 

[Mark Waite]

I don't have help for your specific exception, but advice for a more general case.

Since you remained on 1.652 that long (over a year?), it seems your organization prefers stability over using the most recent release.  That probably means you should upgrade to the Jenkins Long Term Support (LTS) release, rather than the weekly build that you attempted.  The Jenkins LTS release is described at https://jenkins.io/download/ 

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e284f49c-2424-4a5b-871f-900097723475%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.