Summary from Buildsystem BoF at Desktop Summit

[Torgny Nyblom]

On Wed, 17 Aug 2011 09:21:33 +0200, Volker Krause wrote:
> On Monday 15 August 2011 23:31:26 Alexander Neundorf wrote:
>> -----------------------------------------
>> 8) Testing
>> -----------------------------------------
[...]
> ok, so let me explain what I have been working on there.
>
> The idea we came up with in Randa basically is to deploy more or less 
> blank
> Linux VMs in a SETI at Home-style to as many as possible machines. They
> continuously run kdesrc-build with enabled CDash reporting
[...]
> This approach addresses one specific problem of the entire CI topic, 
> namely
> testing as many as possible of the various different build options we 
> have
> (platform profiles, debug vs. release, different dependency versions,
> with or
> without optional dependencies, etc). This does not address testing on
> different OS/platforms etc., so it's only one piece in the puzzle, 
> not the
> single solution.

This sounds like it should be done regardless of the continuous 
integration builds.
As it relies on community / volunteer provided resources on a not known 
time basis (or?).
And there doesn't seem to a trigger to start testing when a change has 
been made as with the more traditional CI testing.
If successful it would be a great way to cover many of the possible 
configurations.


My vision:

A traditional CI system running on KDE HW.
A system like this running configuration tests.
Ideally these should be integrated so that the configuration test 
system only tests builds that have passed the CI system.

/Regards
Torgny