On 09/23/2014 09:45 AM, Johannes Wienke wrote:
> On 09/22/2014 07:05 PM, Daniel Beck wrote:
>> Plugins are developed independently from core and usually have no 'LTS
>> line', except maybe to backport fixes to a version compatible with LTS when
>> the main development line requires a more recent core.
>>
>> Still, most plugins are compatible with 1.565.x. Make sure the date on the
>> lower right of /pluginManager/advanced is recent. If not, press 'Check now'
>> and wait until the page confirms it was updated ("Checking Updates... Done").
>
> Ok, I can see that the last update was months ago. However, clicking
> "check now" just ends up in the "Checking Updates..." page and will
> never return from there.
>
>> Make sure there's an update center configured on /pluginManager/advanced
>> (URL field in Update Site section), it should likely point to
>> http://updates.jenkins-ci.org/update-center.json
>
> I have already checked that. According to
> https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line the URL
> should be http://updates.jenkins-ci.org/stable/update-center.json, which
> I have configured. The funny thing is that if I used curl to access that
> site, I just get a 302 answer with a basically empty web page containing
> a link to
> http://mirrors.jenkins-ci.org/updates/stable/update-center.json. Opening
> the original link in a web browser, however, redirects me correctly to a
> selected mirror.Ok, with the https version of the update site everything works. No idea why... -- Johannes Wienke, Researcher at CoR-Lab / CITEC, Bielefeld University Address: Inspiration 1, D-33619 Bielefeld, Germany (Room 1.307) Phone: +49 521 106-67277
signature.asc
Description: OpenPGP digital signature
