Plugin update confusion
87 views
Skip to first unread message
David Aldrich
May 9, 2012, 6:18:34 AM5/9/12
to jenkins...@googlegroups.com
Hi
I am running Jenkins 1.447.1 LTS. This morning I decided to update the svn plugin from 1.34 to 1.39. I selected the svn plugin update, the download succeeded and I restarted Jenkins.
Now, the plugins updates table is still showing 1.39 available and 1.34 installed. The ‘Installed’ table shows 1.34 installed and a button marked ‘Downgrade to 1.34’ is shown.
Please can anyone explain why 1.39 is not shown as installed, and why Jenkins offers to downgrade to the same version that it thinks is installed?
Best regards
David
Chemmo
May 9, 2012, 11:38:14 AM5/9/12
to Jenkins Users
I'm experiencing this too. I even shut down Jenkins, downloaded the
1.39 update manually, deleted all subversion plugin files and folders
and placed the new one in and its still reporting as 1.34. Perhaps the
metadata for 1.39 is incorrect?
1.39 update manually, deleted all subversion plugin files and folders
and placed the new one in and its still reporting as 1.34. Perhaps the
metadata for 1.39 is incorrect?
Chemmo
May 9, 2012, 11:44:33 AM5/9/12
to Jenkins Users
Coincidentally, I recently built 1.39 (from https://svn.jenkins-ci.org/tags/subversion-1.39/),
so I installed this instead manually and the problem was resolved. So
it seems there is something kooky about the released plugin at
http://updates.jenkins-ci.org/download/plugins/subversion/1.39/subversion.hpi.
By the way, I'm running 1.448
> > David- Hide quoted text -
>
> - Show quoted text -
so I installed this instead manually and the problem was resolved. So
it seems there is something kooky about the released plugin at
http://updates.jenkins-ci.org/download/plugins/subversion/1.39/subversion.hpi.
By the way, I'm running 1.448
>
> - Show quoted text -
Chemmo
May 9, 2012, 4:25:56 PM5/9/12
to Jenkins Users
Ah, this explains it
https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins
On May 9, 4:44 pm, Chemmo <che...@gmail.com> wrote:
> Coincidentally, I recently built 1.39 (fromhttps://svn.jenkins-ci.org/tags/subversion-1.39/),
https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins
On May 9, 4:44 pm, Chemmo <che...@gmail.com> wrote:
> Coincidentally, I recently built 1.39 (fromhttps://svn.jenkins-ci.org/tags/subversion-1.39/),
> so I installed this instead manually and the problem was resolved. So
> it seems there is something kooky about the released plugin athttp://updates.jenkins-ci.org/download/plugins/subversion/1.39/subver....
David Aldrich
May 10, 2012, 3:44:05 AM5/10/12
to jenkins...@googlegroups.com
but the Subversion Plugin is not shown as pinned in my installation ...
David
> Click
> https://www.mailcontrol.com/sr/qhyK36ZW0+!TndxI!oX7Uj4ERLiEw+6O8324
> 9XFnLkaWINsQLRSvpvi8!ENnOqBzL1pp4fXXKWa2eN6FcXjHgg== to report
> this email as spam.
David
> https://www.mailcontrol.com/sr/qhyK36ZW0+!TndxI!oX7Uj4ERLiEw+6O8324
> 9XFnLkaWINsQLRSvpvi8!ENnOqBzL1pp4fXXKWa2eN6FcXjHgg== to report
> this email as spam.
Jan Seidel
May 10, 2012, 4:59:54 AM5/10/12
to jenkins...@googlegroups.com
Update it manually.
create a file named subversion.jpi.disabled and subversion.jpi.pinned
Download the recent svn plugin and give it a different file name. I use subversion-1.39.hpi as name. restart the server.
Jenkins or the plugins (dunno which causes this) has sometimes the annoying habit to show you the plugin with the lowest version number.
I assume that the plugin with the lower version then also is used.
Take care
Jan
create a file named subversion.jpi.disabled and subversion.jpi.pinned
Download the recent svn plugin and give it a different file name. I use subversion-1.39.hpi as name. restart the server.
Jenkins or the plugins (dunno which causes this) has sometimes the annoying habit to show you the plugin with the lowest version number.
I assume that the plugin with the lower version then also is used.
Take care
Jan
Reply all
Reply to author
Forward
0 new messages