[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Thoughts from a former KDE, currently Mozilla developer
From:       Cyrille Berger Skott <cberger () cberger ! net>
Date:       2010-12-09 9:21:22
Message-ID: 201012091021.22082.cberger () cberger ! net
[Download RAW message or body]

On Wednesday 08 December 2010, Thiago Macieira wrote:
> That's a laudable goal and one we do for Qt. We can't test every push,
> though,  simply because that doesn't scale. I have some material I'm
> preparing that I'll share on this subject by the end of the year.
> 
> KDE is much futher back in that. It's not reasonable to say jump from
> where  KDE is to where Mozilla or Qt are. It needs to be a gradual
> process, with a plan.
> 
> For us in Qt, we've had unit tests running for over 7 years. But it wasn't 
> until last year that we had a system that tested the incoming changes and 
> blocked them if a regression happened. Even then, the coverage is very low 
> (around 60% on average) and there are many unstable tests.
> 
> And a proper build farm can cost in the range of millions of dollars. I
> doubt  we can find such a farm for KDE. Donated resources and distributed
> reports are our only option.

Yes it is something I am working on for Calligra. Right now, I have setup a 
continuous build that do post-checking, of both koffice/2.3 and 
calligra/master. But with the move to git I do intend to move to a pre-
checking system. Where people commit to a branch, and then a bot test if it 
can goes into master. And do automatic merging.

But you are quiet right that it does not scale, it is limited to one project 
and one system. To be serious we would need to test on more systems as well. 
But I consider it to be good enough, and I think we also need to encourage 
people to submit report to cdash. It should be made part of our culture :)

-- 
Cyrille Berger Skott
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]