[Buildbot-devel] custom buildstem

[Philippe McLean]

i listed a few practices previously, without getting into the lengthy
motivations

in terms of BB as a framework, and how it operates as a distributed job
execution and reporting framework, and the role of a release engineer/ QA
test engineer in a software team, then we want to

- empower developers to write reliable test automation, and not make
master.cfg central point of contention
- separate mechanisms of test code from policies of branch management
- find bugs in our product, as early as possible, and not be hunting for
them in the build scripts


On Tue, Mar 29, 2011 at 11:41 AM, Dustin J. Mitchell <dustin at v.igoro.us>wrote:

> On Tue, Mar 29, 2011 at 12:22 PM, Philippe McLean
> <philippe.mclean at gmail.com> wrote:
> > I think there is a pattern in here... it seems a bit like MVC
>
> This seems to be a *big* sticking point for release engineers
> everywhere.  If you can identify some best practices or patterns,
> let's get them in the manual!
>
> Dustin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110329/8ea4063a/attachment.html>