Thoughts on Buildbot and on JSON APIs

[Mark Atwood]

Hi!

While I understand and sympathize with Hal's frustration with getting
buildbot to work with Lync, I fully support the Buildbot developers
decision to more fully decouple the UI from the build farm coordinator
demons.   This is a step in the right direction, back to the older and more
correct school of thought that you just shove structured stream data over
the TCP connection, and do the rendering smarts as close to the user as
possible.

There are a number of JSON prettyprinters available.  Refer to
http://stackoverflow.com/questions/352098/how-can-i-pretty-print-json and
embrace and extend their examples with bits of filtering.


The example
curl -X GET -H "Authorization: foo" http://testsite/api/ | python
-mjson.tool
is particularly powerful.  I use it a lot to bang directly on OpenStack
APIs.

A super powerful tool is jq, aka "SED for JSON".
https://stedolan.github.io/jq/

I see that Amar is going to write a short tool to display test run pass
info from our buildbot array.  Thank you Amar.  Let us all know when it's
working, and make it as brutally simple as possible.

..m
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/devel/attachments/20151201/7b956e18/attachment.html>