[Buildbot-devel] 0.7.x community?

Dmitry Nezhevenko dion at dion.org.ua
Wed May 30 09:15:33 UTC 2012

On Tue, May 29, 2012 at 08:40:37PM -0500, Dustin J. Mitchell wrote:
> I'm aware that upgrading a Buildbot instance with custom code can be
> difficult.  This is mostly because the APIs against which such code is
> written were ad-hoc, undocumented, and poorly implemented.  It's also
> due to the lack of development and staging instances in most Buildbot
> deployments, making an upgrade difficult to test; and to the divided
> attentions of most build / release engineers.  As a result, we've got
> users stalled on just about every release -- 0.8.3 seems particularly
> popular, as do 0.7.10 and 0.7.12.

Personally I've stuck with 0.8.5. Just because it "just works". At the
same time we've a lot of small/random changes to both master and slave
that are probably not acceptable to mainline. And a few large enough

- 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

- custom ChangeSource for AccuRev

- "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.

- A few other hacks.

WBR, Dmitry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://buildbot.net/pipermail/devel/attachments/20120530/5d43df66/attachment.bin>

More information about the devel mailing list