[JIRA] [core] (JENKINS-12514) .hpi versus .jpi causes inability to upgrade Subversion Plugin

[mar...@mbs3.org (JIRA)]

Title: Message Title

Martin Smith edited a comment on JENKINS-12514   Re: .hpi versus .jpi causes inability to upgrade Subversion Plugin Hello! I'm still seeing this on the latest Jenkins LTS 1.609.3 (2015/09/02) as well. I've documented a lot of it in an issue filed against [the Chef cookbook for Jenkins](https://github.com/chef-cookbooks/jenkins/issues/406), but the core of the issue is this: { { code:java} # sha256sum /var/chef/cache/cvs-2.12.plugin  6e6dfd35e8501bf5f84a9d43d210db61165ce51a606327fc81f2efc5208478ba  /var/chef/cache/cvs-2.12.plugin # unzip /var/chef/cache/cvs-2.12.plugin # grep -i plugin-version META-INF/MANIFEST.MF  Plugin-Version: 2.12 # sha256sum /var/lib/jenkins/plugins/cvs.jpi  6e6dfd35e8501bf5f84a9d43d210db61165ce51a606327fc81f2efc5208478ba  cvs.jpi # grep -i plugin-version /var/lib/jenkins/plugins/cvs/META-INF/MANIFEST.MF  Plugin-Version: 2.11 # mv /var/lib/jenkins/war/WEB-INF/plugins/cvs.hpi /tmp/nonchef-cvs.hpi # service jenkins restart ok: run: jenkins: (pid 14918) 1s # grep -i plugin-version /var/lib/jenkins/plugins/cvs/META-INF/MANIFEST.MF  Plugin-Version: 2.12 {code } } As you can see, Jenkins won't upgrade the plugin, even though it's a newer version, until I manually remove the .hpi and restart Jenkins. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.