This is a screenshot of the current kdepimlibs build status on CDash. In the first column you can see the different build setups that have committed a build. There are builds from FreeBSD, SunOS, Linux, with different kind of CMake versions and differnt versions of GCC.

After that you can see the results of the different stages of the build: Update, Configure, Build and the Tests. The ‘Min’ column indicates how long that stage took. The most interesting column for me are the warnings in the build section. I’m trying to get that number down to the real warnings, removing all the non interesting warnings. On some line you can see 8 with -20 just below it. That means that in the last run the amount of warnings dropped from 28 to 20. Simalary you can see that there currently is a build error on one of the build machines…

CDash provides the possibility to subscribe to projects, with that subscription you can automatically receive build errors if you like to. You can also indicate that you only want to receive mail when your svn account is one of the possible causes of a build failure.

Contributing your build to the dashboard is easy. Just start your build as usual with cmake. Then instead of typing ‘make’, type ‘ctest -D Experimental’. It will build it and upload the data to CDash automatically.

So, next time your build fails and you need help on IRC, you might as well through your build on CDash and put the link to your build on IRC. Nightly builds are also important. It would be nice if we get as much as possibile different setups to report there. That would make releasing a KDE SC easy, as we can have detected build errors on certain platforms in a very early stage.

Summarized:

• Please contribute builds to dashboards
• Subscribe to build errors for your pet project
• Module maintainers should monitor their module
• If you have a minuted, fix some build warnings, it is fun!