[
https://issues.jenkins-ci.org/browse/JENKINS-12632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Milliken reopened JENKINS-12632:
-------------------------------------
Just re-tested with a fresh setup of Jenkins 1.456 on Fedora. Very simply
setup, just grabbed the .war file and ran it.
After first startup, the plugin folder contained subversion.jpi, which had a
reported version of 1.34
paul.milliken@besaid ~/.jenkins/plugins $ ls subversion.*
subversion.jpi
paul.milliken@besaid ~/.jenkins/plugins $ unzip -p subversion.jpi
META-INF/MANIFEST.MF | grep Plugin-Version
Plugin-Version: 1.34
Update manager reported that 1.39 was available. Told it to download and
install after restart (but not to restart automatically). After the download,
had subversion.jpi and subversion.bak (as expected), with the appropriate
versions.
paul.milliken@besaid ~/.jenkins/plugins $ ls subversion.*
subversion.bak subversion.jpi
paul.milliken@besaid ~/.jenkins/plugins $ unzip -p subversion.jpi
META-INF/MANIFEST.MF | grep Plugin-Version
Plugin-Version: 1.39
paul.milliken@besaid ~/.jenkins/plugins $ unzip -p subversion.bak
META-INF/MANIFEST.MF | grep Plugin-Version
Plugin-Version: 1.34
Restarted jenkins.
paul.milliken@besaid ~/.jenkins/plugins $ ls subversion.*
subversion.bak subversion.jpi
paul.milliken@besaid ~/.jenkins/plugins $ unzip -p subversion.jpi
META-INF/MANIFEST.MF | grep Plugin-Version
Plugin-Version: 1.34
paul.milliken@besaid ~/.jenkins/plugins $ unzip -p subversion.bak
META-INF/MANIFEST.MF | grep Plugin-Version
Plugin-Version: 1.34
It looks like the update is still failing to be automatically pinned, resulting
in the bundled version overwriting it. Manually pinning the plugin (by creating
subversion.jpi.pinned) works.
> Subversion plugin update fails
> ------------------------------
>
> Key: JENKINS-12632
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12632
> Project: Jenkins
> Issue Type: Bug
> Components: cvs, plugin, subversion, update-center
> Environment: Jenkins 1.450
> CentOS 6.2 (2.6.32-220.4.1.el6.centos.plus.x86_64)
> java version "1.6.0_29"
> Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode)
> Reporter: Paul Milliken
> Labels: jenkins, plugin
>
> 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.
--
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
