User:Rhelmer:Buildbot/Tinderbox server parity
Buildbot acting as a Tinderbox client (that is, send an email when each Builder starts/finishes to the Tinderbox server) has many advantages over using the usual Tinderbox client. For instance:
- real-time logs
- web stop/force build
- reliable error checking/logging
- active community
However, on the server side, Tinderbox server still has advantages over Buildbot server:
- supports multiple "trees"
- easily editable status pages
- hooked into bonsai's "tree close" system
- no hard dependency between client and server
The last point is an important one, and there are two major concerns:
- an exploit to Buildbot server gives control over all clients
- current Tinderbox server gets a lot of load; if Buildbot server goes down, all builds stop
We are planning on addressing the last point by adding static caching to Buildbot, so regular users only see a static representation, and only trusted users can access the server directly.
The rest of the points can be dealt with by either adding features to Buildbot, putting them elsewhere, or foregoing them completely (I've only listed the ones that I think we should definitely carry over, there are many more Tinderbox server features that may not be useful enough to bother with).
