on Wed Aug 08 2007, Stefan Seefeld <seefeld-AT-sympatico.ca> wrote:
David Abrahams wrote:
This part of my analysis focuses on the tools available for getting feedback from the system about what's broken. Once again, because there's been substantial effort invested in dart/cmake/ctest and interest expressed by Kitware in supporting our use thereof, I'm including that along with our current mechanisms. Although not strictly a reporting system, I'll also discuss BuildBot a bit because Rene has been doing some research on it and it has some feedback features.
I think it is important to consider the different tools for the purpose they were designed for. None of them will do the whole job, but with a good combination of them I believe very useful and robust things can be built.
Notably, I do believe that buildbot is an invaluable tool to drive the build and test automation. It provides a good framework to formalize the process in, and it scales very well.
As I mentioned, I plan to deal with that issue in a separate thread of this analysis. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com