Grrr... did I use the word "RESTful"? I normally try to avoid using
that as it usually ends up in a debate :)
Let me phrase it the way I should have... from what I know so far, I
don't think the Jenkins API would work with the likes of AngularJs
$resource
(https://docs.angularjs.org/api/ngResource/service/$resource). I think
the mechanism for navigating the object graph (tree, xpath, depth etc)
would be the problem. I may be wrong on that since my experience of
using the Jenkins API is fairly limited.
That said... I personally don't think that matters all that much for the
core Jenkins UI. I think no matter what we do with the core UI, there
would be a good argument to be made for staying away from such
frameworks, in which case we'd just perform bog standard ajax rpc calls
from the UI. Where it might cause headaches is for people building
their own custom interfaces on the Jenkins API and they want to use
something like AngularJS ($resource + other bells and whistles). I
think this was the point that Tyler was making.
On 02/06/2014 21:23, Jesse Glick wrote:
On Thu, May 29, 2014 at 3:37 AM, Tom Fennelly <[email protected]> wrote:
These only work however if the API is truly restful. I'm
fairly sure they would not work with the Jenkins API.
What specifically about the Jenkins remote API do you find RESTless?
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
