#2359: Support extracting steps from annotated logs
------------------------+-----------------------
Reporter: dank | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: undecided
Version: master | Keywords:
------------------------+-----------------------
In general, putting too much knowledge about how builds are
done into buildbot config files is considered harmful because
it makes it hard for non-buildbot-admins to update or test the
build procedure used by buildbot.
One approach to dealing with this is to have buildbot run a single
step that just runs a script that is under full control of the
developers (as opposed to buildbot admins). That's good, but
then you lose visibility into build steps, and the waterfall is
a bit more opaque.
Chromium currently does this, and solves the big-opaque-single-step-
waterfall problem by parsing the logfile and synthesizing steps from
annotations inserted into the log by the build script.
See
http://lackingrhoticity.blogspot.com/2011/08/fixing-trouble-with-
buildbot.html
for discussion, and code and tests at
http://src.chromium.org/svn/trunk/tools/build/scripts/master/chromium_step.py
http://src.chromium.org/svn/trunk/tools/build/scripts/master/unittests/annotator_test.py
This seems like a Good Idea. Any chance it could be merged into
buildbot proper?
--
Ticket URL: <http://trac.buildbot.net/ticket/2359>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
