I'm encountering an issue similar to JENKINS-12514 with Jenkins 1.450.
Update manager reports that I'm running subversion plugin 1.34 and 1.37 is available. In my plugins folder I can see:
rw-rw-r-. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.bak
rw-rw-r-. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.jpi
I tell Jenkins to install 1.37. Once it's downloaded I can see:
rw-rw-r-. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.bak
rw-rw-r-. 1 jenkins jenkins 2103308 Feb 2 15:43 subversion.jpi
Checking the manifests:
[jenkins@XXXX plugins]$ unzip -p subversion.bak META-INF/MANIFEST.MF | grep Plugin-Version
Plugin-Version: 1.34
[jenkins@XXXX plugins]$ unzip -p subversion.jpi META-INF/MANIFEST.MF | grep Plugin-Version
Plugin-Version: 1.37
Restart jenkins to apply the changes. At this point, the present files are:
rw-rw-r-. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.bak
rw-rw-r-. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.jpi
and the manifests:
[jenkins@XXXX plugins]$ unzip -p subversion.bak META-INF/MANIFEST.MF | grep Plugin-Version
Plugin-Version: 1.34
[jenkins@XXXX plugins]$ unzip -p subversion.jpi META-INF/MANIFEST.MF | grep Plugin-Version
Plugin-Version: 1.34
And update manager still reports 1.34 with 1.37 available.
- is related to
-
JENKINS-12514 .hpi versus .jpi causes inability to upgrade Subversion Plugin
-
- Resolved
-
-
JENKINS-13129 Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
-
- Resolved
-
I've also just tried with the CVS plugin (1.6 -> 2.0 upgrade) and observe the same behaviour, so it isn't specific to the subversion plugin. Seems more likely to be a generic issue with bundled plugins.
I've now tried manually creating a subversion.jpi.pinned file, then it seems to work. This doesn't match up with the behaviour described on https://wiki.jenkins-ci.org/display/JA/Pinned+Plugins, which implies that manually updating a
pinnedbundled plugin should automatically pin it to prevent overwriting.