#921: buildmaster logging should be more segregated
------------------------+--------------------
Reporter: bhearsum | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.8.+
Version: 0.8.0 | Resolution:
Keywords: |
------------------------+--------------------
Comment (by dustin):
This is pretty hard to do, and would make correlating events even harder,
since you only get second-level granularity in the logfiles.
I think a better fix is to adjust the kind of logging that builds do.
Right now, there's a lot of redundant information about which methods are
being called, and very little useful information. That could probably be
condensed down to one line (starting step 'foo' of 'buildername' build
#NNN), which would make things a bit easier to follow.
--
Ticket URL: <http://trac.buildbot.net/ticket/921#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
