#2706: Handling test results
-------------------------+--------------------
Reporter: jpommerening | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: 0.8.+
Version: 0.8.8 | Resolution:
Keywords: |
-------------------------+--------------------
Comment (by dustin):
In 0.8.x, logs are stored as netstrings in the filesystem, with one file
per log. The naive way to port that to the DB, and still allow per-line
access, would be to put each line in a DB row. And yes, messages are
related to nine's MQ stuff.
If this test support is optional, meaning that users won't find themselves
surprised by a 20GB sqlite DB and a slow master, then it might be OK to go
ahead and implement this in a fairly naive fashion, maybe a table with
columns (buildid, testname, result, logid, logline). If that proves
inefficient, we can revisit and optimize.
--
Ticket URL: <http://trac.buildbot.net/ticket/2706#comment:3>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
