On Saturday 14 April 2012, Laszlo Papp wrote: > > Afterwards it runs cppcheck on the source code... > > That is a really nice advantage, if it can be integrated with handy > tools. Although, I would personally like to use much more advanced and > useful tools than cppcheck. > > [...] > > > But overall these are two very useful solutions which do not compete with > > each other and we should make use of them in a useful combined way, e.g. > > by submitting build results from build.kde.org to CDash. > > Fair enough, thanks. > > One additional comment on my side is that, if I read these lines on > the jenkins website, I have the impression Jenkins can cover the use > case of CDash in the sense of running the build from cron jobs:
I think cdash can do more than you (and me) know. I know there is the so called cdash@home feature, which can kind of trigger builds on machines. It can also be integrated with gerrit. Here Marcus explains the setup Kitware is using: http://www.kitware.com/source/home/post/62 Alex
