Build Server web interface

[Alexander Neundorf]

On Monday 12 October 2009, Patrick Spendrin wrote:
> Alexander Neundorf schrieb:
> > On Sunday 11 October 2009, Patrick Spendrin wrote:
> >> Alexander Neundorf schrieb:
> >
> > ...
> >
> >> Ok, I'll check this stuff, I don't know if we really want to disturb the
> >> programmers already though ;-)
> >> This seems like it would keep submissions open to e.g. only include
> >> ctest_test too?! This way it would be rather easy to integrate for us
> >
> > It seems so, but I didn't try it.
> >
> >> (Simply write a small script and off we go - even ctest_update could be
> >> run before).
> >> I will see if I can get ctest to work this way.
> >
> > Let me know which issues you find (I'm quite sure there will be some)
>
> Ok, I just played around a bit and it seems we can maybe even have a bit
> more: if I just run ctest from the test directory instead of nmake test
> I can run all tests and submit them to the dashboard including the build
> results (there seems to be kind of a rebuild before). The basic point is
> now where to submit all the results to (I have found automoc, kdelibs,
> kdepimlibs but not much more; I added myself akonadi because it has tests).

Yes, that's another open question.
We can build e.g kdesupport all-in-one, and we can build everything 
separately.
What do we/you want to have on the dashboard ?
Similar for kdebase (workspace/runtime/apps) and maybe others.

Alex