Microsummaries + performance data = a Sheriff's best deputy?
I found Myk's XTech talk on microsummaries very interesting.
Last night at dinner, I believe it was Axel who was suggesting that publishing tinderbox performance data as an RSS feed might offer some interesting possibilities.
At first, I didn't see the point of doing that exactly, but with microsummaries, a tree sheriff could put all the branches they're supposed to be watching in their toolbar, so they wouldn't have to scan a huge tinderbox page all day. Could maybe even whip up some XSLT (was it?) to make them change colors if the performance numbers jump outside of some pre-defined range.
Of course, the cool thing about microsummaries is you don't necessarily need the RSS feed, it sounds like.
It's an interesting idea, though... is there a more consumable format for perf data than we currently offer/publish?
Comments
we do something similiar at OSAF - but instead of an RSS feed we inserted a table of the key performance tests into the status page.
http://builds.osafoundation.org/tinderbox/Chandler/status.html
Posted by: bear | May 17, 2006 3:59 PM
Was thinking just this morning that microsummaries might be able to replace the tinderstatus extension
Posted by: A`ja | May 17, 2006 8:11 PM
I definitely think we should try to publish the perf data in an XML format for automated processing (it can be XHTML and viewable too). Then microsummarizing or turning it into SVG graphs or doing whatever with it would be a lot easier.
Posted by: Benjamin Smedberg | May 19, 2006 7:17 AM