In case anyone considers working on this please also consider
https://issues.jenkins-ci.org/browse/JENKINS-26231 :)
Thanks! Br,
Christoph
On Friday, December 4, 2015 at 10:04:39 PM UTC+1, Richard Bywater wrote:
>
> Can I suggest we change the content type to application/javascript then at
> lea
Can I suggest we change the content type to application/javascript then at
least so at least one part is correct? :) (if it doesn't break anything
obviously)
Richard
On Sat, 5 Dec 2015 5:04 am 'Jesse Glick' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> On Fri, Dec 4, 2015 at
On Fri, Dec 4, 2015 at 4:48 AM, Richard Bywater wrote:
> is it documented why it advertises itself as JSON but actually isn't?
It is JSONP. Yes it should have been named `update-center.js` to
match, but existing Jenkins installations expect JSONP from this URL
so it is too late to change it.
(BT
Just taking a look at that file I'm surprised its like that - is it
documented why it advertises itself as JSON but actually isn't? Breaks all
the rules :)
Richard.
On Fri, 4 Dec 2015 at 22:45 Manuel Holzleitner
wrote:
> Sorry, I missed to pipe the file through sed '1d;$d' to remove the
> non-J
Sorry, I missed to pipe the file through sed '1d;$d' to remove the non-Json
lines at the beginning and at the end of the file
On Friday, December 4, 2015 at 10:39:43 AM UTC+1, Manuel Holzleitner wrote:
>
> Hello,
>
> I get the plugin infos by retrieving the
> http://updates.jenkins-ci.org/update
Hello,
I get the plugin infos by retrieving the
http://updates.jenkins-ci.org/update-center.json file and downloading it to
/var/lib/jenkins/updates/default.json.
However, this does not work anymore as I get a parse exception now:
Dec 04, 2015 9:28:46 AM SEVERE hudson.model.UpdateSite getJSONObj
