<html lang="en">
<head>
<title>Writing New BuildSteps - BuildBot Manual - 0.8.4p1</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="BuildBot Manual - 0.8.4p1">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Build-Steps.html#Build-Steps" title="Build Steps">
<link rel="prev" href="Miscellaneous-BuildSteps.html#Miscellaneous-BuildSteps" title="Miscellaneous BuildSteps">
<link rel="next" href="Build-Step-Index.html#Build-Step-Index" title="Build Step Index">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
This is the BuildBot manual for Buildbot version 0.8.4p1.
Copyright (C) 2005, 2006, 2009, 2010 Brian Warner
Copying and distribution of this file, with or without
modification, are permitted in any medium without royalty
provided the copyright notice and this notice are preserved.-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
--></style>
</head>
<body>
<div class="node">
<a name="Writing-New-BuildSteps"></a>
<p>
Next: <a rel="next" accesskey="n" href="Build-Step-Index.html#Build-Step-Index">Build Step Index</a>,
Previous: <a rel="previous" accesskey="p" href="Miscellaneous-BuildSteps.html#Miscellaneous-BuildSteps">Miscellaneous BuildSteps</a>,
Up: <a rel="up" accesskey="u" href="Build-Steps.html#Build-Steps">Build Steps</a>
<hr>
</div>
<h4 class="subsection">4.12.13 Writing New BuildSteps</h4>
<p>While it is a good idea to keep your build process self-contained in
the source code tree, sometimes it is convenient to put more
intelligence into your Buildbot configuration. One way to do this is
to write a custom BuildStep. Once written, this Step can be used in
the <samp><span class="file">master.cfg</span></samp> file.
<p>The best reason for writing a custom BuildStep is to better parse the
results of the command being run. For example, a BuildStep that knows
about JUnit could look at the logfiles to determine which tests had
been run, how many passed and how many failed, and then report more
detailed information than a simple <code>rc==0</code> -based “good/bad”
decision.
<ul class="menu">
<li><a accesskey="1" href="Writing-BuildStep-Constructors.html#Writing-BuildStep-Constructors">Writing BuildStep Constructors</a>
<li><a accesskey="2" href="BuildStep-LogFiles.html#BuildStep-LogFiles">BuildStep LogFiles</a>
<li><a accesskey="3" href="Reading-Logfiles.html#Reading-Logfiles">Reading Logfiles</a>
<li><a accesskey="4" href="Adding-LogObservers.html#Adding-LogObservers">Adding LogObservers</a>
<li><a accesskey="5" href="BuildStep-URLs.html#BuildStep-URLs">BuildStep URLs</a>
</ul>
</body></html>
