After noticing the 'announce' plugin, it occurred to
me that folks (and processes) doing really long builds
sometimes wish they could interrogate a build while
it's running without having to tail a console.
What if Gradle maintained its internal state via MBeans,
and optionally fired up an MBeanServer?
That way, folks could write anything from fancy GUIs
(or Jconsole) to command line state interrogators,
tricked-out plugins for Jenkins, etc. Obviously,
something like this could support smart build farms
pretty nicely -- even "work stealing"! :D
Plainly, JSR-160 connectors to MBeans are nice for java but
aren't particularly friendly for non-java clients. That said,
I just noticed interesting-looking project called "Jolokia"
(Apache License) which gives REST access access to MBeans.
That seems quite cool, if it actually works well.
Overview:
"Jolokia is a fresh way for accessing JMX MBeans remotely.
It is different to JSR-160 connectors in so far as it is
an agent based approach which uses JSON over HTTP for
its communication in a REST-stylish way.
...
Jolokia can operate in an agentless mode where the only
requirement on the target platform is the standard JSR-160
export of its MBeanServer. A proxy listens on the front side
for Jolokia requests via JSON/HTTP and propagates these to
the target server through remote JSR-160 JMX calls. Bulk
requests gets dispatched into multiple JSR-160 requests on
the proxy transparently."
See: http://www.jolokia.org/
http://www.jolokia.org/reference/html/index.html
https://github.com/rhuss/jolokia
https://github.com/rhuss/jolokia/issues
Freenode: #jolokia
Curious to hear what you think.
Cheers,
-Jon
PS:
Hopefully, it's 100% clear that I'm not endorsing the Jolokia project
in any way just yet. I haven't tried it -- this is brainstorming.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
