Sent: 09 May 2012 21:26
> > To: Jenkins Users
> > Subject: Re: Plugin update confusion
> >
> > Ah, this explains it
> >
> > https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins
> >
> > On May 9, 4:44 pm, Chemmo wrote:
> >
.com] On Behalf Of Chemmo
> Sent: 09 May 2012 21:26
> To: Jenkins Users
> Subject: Re: Plugin update confusion
>
> Ah, this explains it
>
> https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins
>
> On May 9, 4:44 pm, Chemmo wrote:
> > Coincidentally, I rece
Ah, this explains it
https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins
On May 9, 4:44 pm, Chemmo 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 t
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/subvers
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 wrote:
> Hi
>
> I am r
