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/), > 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.... > By the way, I'm running 1.448 > > On May 9, 4:38 pm, Chemmo <che...@gmail.com> wrote: > > > > > > > > > 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? > > > On May 9, 11:18 am, David Aldrich <david.aldr...@emea.nec.com> wrote: > > > > 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- Hide quoted text - > > > - Show quoted text -
