[Buildbot-devel] 0.7.x community?

[Tom Prince]

Dmitry Nezhevenko <dion at dion.org.ua> writes:

> - module for custom proprietary VCS (AccuRev). Still client-side. I'm
>   working on general "command"-based master step that I'll try to ask for
>   merge.

Do you mean slave-side? It is fairly straightforward, and probably
easiest, to write new VCS steps as master-side steps. Unless you
*always* run the same commands, which likely isn't the case (for
example, initial checkout), there needs to be some logic around getting
the repository in the right state. If that code lives on the master, it
is much easier to depoly, than if each slave needs custom code.

> - "Aggregate" build step that can contain a few child build steps and
>   execute them one after another. Mostly done to avoid very huge amount of
>   steps in WebStatus. Now it mostly looks like one step per high-level
>   target and each substep just produces own logfiles. Very useful if we've
>   for example 10 targets and each requires something like "configure,
>   make, run tests, create tarball, upload file". I don't think that it can
>   be merged, but can try to cleanup and ask for this if somebody needs it.

There are a couple of other approaches to this.
1) You can run multiple commands per build step, something like
https://github.com/Jc2k/buildbot_travis

2) You can run a script that outputs different phases to different log
files, and then include all those log files (or similarily, have the
output parseable, and do the parsing on the server side).
https://github.com/tomprince/buildbot-configs/blob/notmuch/notmuch_test.py
is a somewhat simple example of the later (but only running a single command).

  Tom