David Abrahams wrote:
Was CTest and CDash ever tried out to see how useful they could be?
I think everyone agreed that CDash's presentation of results is not
really appropriate for Boost. If I had more time right now I'd dig up
the emails from troy on it, but I think you can get a lot from the
boost-cmake list archives.
That said, we have a large software project with similar needs as Boost
interested in adding some features that might change that. Of course
none of this is implemented yet, but in the next 3 to 4 months CDash
maybe in a much better position to work with Boost. I will keep you
posted.
If you had some specifics, it might be helpful to guide us as we add new
features to CDash. So, if either you and/or Troy could send me a
summary of features that you would like to see, it would be helpful. I
remember some of your requests from when we talked in Boston, but that
was a while ago...
The features we are thinking about adding include:
- extend ctest to be able to build/report one package at a time
- extend cdash to support the display of subsets of packages and
dashboards.
Basically, handle an over all view (like now), and a sub-project view of
test results. So, if you are the developer of package A, you do not
need to be bothered with failures in package B if you do not directly
depend on it. As I recall that was the big thing CDash was lacking from
the Boost perspective.
-Bill
_______________________________________________
Boost-cmake mailing list
Boost-cmake@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
