Comments on: CDash Build Dashboard: use it!

By: Marcus D. Hanwell

Marcus D. Hanwell — Sun, 17 Jan 2010 19:43:52 +0000

I will be talking about this today at Camp KDE. I think this is something we should be adding to more KDE modules, and I will be adding my machine when I get back home.

By: Pawel

Pawel — Sat, 16 Jan 2010 21:08:59 +0000

@Toma,

Ok, thank you :)

By: toma

toma — Sat, 16 Jan 2010 20:05:07 +0000

Hit ‘previous’, their daybreak moment is not obvious ;-)

By: bbigras

bbigras — Sat, 16 Jan 2010 20:03:29 +0000

It’s weird, I don’t see data anymore on the dashboard, I only see ‘No update data as of 2010-01-16T14:00:00 EST’

By: Alex

Alex — Sat, 16 Jan 2010 18:20:58 +0000

Why 2.6.2 ? Because this is the version required to build KDE (since 4.2.0 up to 4.4.x).

If you are interested in contributing Nightly builds, please drop by on kde-buildsystem@kde.org and I’ll help you setting it up.

Currently there are dashboards set up for:
* kdesupport
* kdelibs
* kdepimlibs
* kdepim
* kdebase
* kdeutils
* kdeexamples
* kdeadmin
* kdeaccessibility

There’s no special reason why there is no dashboard for the other modules yet, I just didn’t get around to set them up yet.
We’re still fiddling around with setting up fine grained email notification in case of issues (which we have currently every day), so this will still improve.

Alex

By: pvandewyngaerde

pvandewyngaerde — Sat, 16 Jan 2010 17:32:11 +0000

http://my.cdash.org/viewDynamicAnalysis.php?buildid=45116

Anyone know where those are and how to fix the mem leaks ?

By: toma

toma — Sat, 16 Jan 2010 16:34:57 +0000

It works in most kde modules, simply see if there is a CTestConfig.cmake there. As it is should be a separate clean build to catch all the warnings, it does not integrate completely in the current workflow. I’m still not sure what the best way is, I’m sure someone else can answer it better than me. I just run it in a module when i want to work on a module, but nightly builds would be best i guess.

By: Dakon

Dakon — Sat, 16 Jan 2010 16:34:53 +0000

“make Experimental” should also work insted of “ctest -D Experimental”.

By: bbigras

bbigras — Sat, 16 Jan 2010 16:27:34 +0000

Does this works with every KDE module?

And should we put this in our build script to use it every time?

By: toma

toma — Sat, 16 Jan 2010 15:31:46 +0000

It is good to test compilation also with the minimum cmake version kde supports. That way we can detect usage of features of cmake which are not supported in older versions of CMake while KDE should still build with it.