[
https://issues.jenkins-ci.org/browse/JENKINS-12632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159083#comment-159083
]
C. S. commented on JENKINS-12632:
---------------------------------
I have the same problem since 1.450.
I have tried different ways to force the update, it seems that jenkins is
downloading the jpi files from somewhere and there is only the old version
available.
If you delete under plugins subversion and cvs, you would think it fetches the
newest one, but that isn't correct.
It is always the old version.
Another way I have tried was over the plugin manager, I have downloaded the
packages checked the versions from the new jpi files and saved them.
After that I have stopped jenkins and removed all plugin stuff. I uploaded the
new jpi files and started the server.
But it replaces automatically all jpi files with the old ones and I don't know
from where Jenkins is getting them.
> Subversion plugin update fails
> ------------------------------
>
> Key: JENKINS-12632
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12632
> Project: Jenkins
> Issue Type: Bug
> Components: 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
