Setting up a Quality Team within KDE
mgraesslin at kde.org
Mon Apr 9 13:05:28 BST 2012
On Monday 09 April 2012 13:15:26 Andreas Pakulat wrote:
> > There is not only Jenkins, but also CDash, which integrates nicely with
> > our
> > cmake-based build system.
> > I was trying to set up nightly builds for the KDE modules two years ago or
> > so (hosted on http://my.cdash.org, some of our projects are actually
> > using it), gave a talk at Akademy in Tampere and tried really hard, but
> > there was not much response to it.
> Well, I'd say jenkins has a lot more to offer than cdash. Its also a lot
> simpler to use, setup and understand for newcomers in my opinion. With
> jenkins I can have a shell-script job which runs cmake && make && make
> test and be done. Setting up a build for submission to cdash takes a lot
> more effort - at least it did when I tried to do this maybe things got
> easier meanwhile.
I quite agree. Jenkins offers in my opinion much, much more. I have been using
my own custom Jenkins installation for at least half a year now and that
allows me to easily build KWin with various compile flags, etc. etc. Also the
community around Jenkins is very active and there are lots of plugins
available to improve the testing (e.g. cppcheck which got recently added to
our build.kde.org instance)
> PS: Personally I find the Web-GUI also a bit nicer, but thats really just a
> personal preference.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel