The annotator allows your project to generate buildbot build stages as it runs, simply by emitting special tags to stdout/stderr.
This allows you to capture you build process in a single root level script, run it locally, and have your process branch with the project.
Here are a list of the currently supported annotations:
Add a new step <stepname>. End the current step, marking with last available
Add a link with label <label> linking to <url> to the current stage.
Mark the current step as having warnings (orange).
Mark the current step as having failed (red).
Mark the current step as having exceptions (magenta).
Reset the text description of the current step.
Reset the text summary of the current step.
Append <msg> to the current step text.
Append <msg> to the step summary (appears on top of the waterfall).
Halt if exception or failure steps are encountered (default is not).
Honor the return code being zero (success), even if steps have other results.
Environment Variables passed into annotated steps:
Names of users who triggered the build %(blamelist:-)s.
Name of the branch that this was triggered on %(branch:-None)s.
Name of the buildbot builder %(buildername:-None)s.
Build number of the current build (unique when combined with BUILDBOT_BUILDERNAME for one master, unless master database is reset) %(buildnumber:-None)s.
Set to '1' if clobber was set on the tryjob or force build check-box was checked %(clobber:+1)s.
Current gotten revision to the best of buildbot's knowledge, may be empty %(got_revision:-None)s.
Current revision to the best of buildbot's knowledge, may be empty %(revision:-None)s.
Name of the scheduler managing this builder %(scheduler:-None)s.
The current builder's name, as described in buildbot config %(slavename:-None)s.
Equivalent to @@@STEP_WARNINGS@@@
Equivalent to @@@STEP_FAILURE@@@
Equivalent to @@@STEP_EXCEPTION@@@
Equivalent to @@@STEP_LINK@<label>@<url>@@@