[
https://issues.jenkins-ci.org/browse/JENKINS-12514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158921#comment-158921
]
Alex Lehmann commented on JENKINS-12514:
----------------------------------------
I had to set up a "fresh" jenkins instance for dev testing, so I had a new
chance to check if updating the plugins works or not, it turns out it doesn't.
The file is updated in the plugin directory, but the .pinned file is not
created so that old plugin is reinstalled when restarting the server.
When I create the .pinned files manually after shutting down the server, the
update works, that provides a work-around at least.
> .hpi versus .jpi causes inability to upgrade Subversion Plugin
> --------------------------------------------------------------
>
> Key: JENKINS-12514
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12514
> Project: Jenkins
> Issue Type: Bug
> Components: update-center
> Environment: Ubuntu 11.10, OpenJDK 1.6.0_23, Tomcat 7.0.21, Jenkins
> 1.448 & 1.449
> Reporter: Charlie Huggard
> Assignee: Kohsuke Kawaguchi
> Priority: Minor
>
> Reproduction:
> $JENKINS_HOME/plugins: subversion (directory), subversion.hpi
> 1) Open http://<root>/pluginManager. Update Subversion plugin from 1.34 ->
> 1.37 using download now and install after restart button.
> $JENKINS_HOME/plugins: subversion (directory), subversion.bak (1.34),
> subversion.hpi.pinned, subversion.jpi (1.37)
> 2) Restart Tomcat/Jenkins
> $JENKINS_HOME/plugins: subversion (directory), subversion.bak (1.34),
> subversion.hpi (1.34) subversion.hpi.pinned, subversion.jpi (1.37)
> 3) PluginManager still reports old version
> Should note that the logs report:
> INFO: Ignoring /ci/jenkins-home/plugins/subversion.jpi because
> /ci/jenkins-home/plugins/subversion.hpi is already loaded
> Also the plugin is broken at this point with a NoClassDefFound on
> org/tmatesoft/svn/core/SVNException
> Clean State:
> 1) /etc/init.d/tomcat7 stop
> 2) cd $JENKINS_HOME/plugins
> 3) rm subversion*
> 4) /etc/init.d/tomcat7 start
> Workaround:
> 1) Restore clean state
> 2) Update plugin
> 3) Stop tomcat/jenkins
> 4) cd $JENKINS_HOME/plugins
> 5) mv subversion.jpi subversion.hpi
> 6) Start tomcat/jenkins
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
