CMake and xml output

[Torgny Nyblom]

On Sunday 01 May 2011 20.58.11 Alexander Neundorf wrote:
> On Sunday 01 May 2011, Torgny Nyblom wrote:
> > On Sunday 01 May 2011 19.07.11 Alexander Neundorf wrote:
> > > On Saturday 30 April 2011, Torgny Nyblom wrote:
> > > > On Saturday 30 April 2011 18.20.07 Alexander Neundorf wrote:
> > > > > Hi,
> > > > > 
> > > > > On Saturday 30 April 2011, Torgny Nyblom wrote:
> > > > > > Hi,
> > > > > > 
> > > > > > I'm experimenting with setting up a continious
> > > > > > integration
> > > > > > server for
> > > > > > kdepim*. Everything seems to work ok except for
> > > > > > collecting the
> > > > > > results from CTest. If I understand the documentation
> > > > > > correct
> > > > > > CTest should produce a collection of .xml files as
> > > > > > result but
> > > > > > all I see is three plain text files. Does anyone here
> > > > > > know why
> > > > > > and hopefully how I can change this?
> > > > > 
> > > > > great that you want to set this up.
> > > > > What do you want to do with the xml result files from ctest
> > > > > ?
> > > > > If you simply use cdash, and there are already projects for
> > > > > kdepim
> > > > > set up on my.cdash.org, everything should just work.
> > > > > 
> > > > > Are you trying to do something different ?
> > > > > 
> > > > > If so, why ?
> > > > 
> > > > I'm trying to set up the whole push->build->test chain and if I
> > > > understood CDash correctly that is just for showing results.
> > > > Which
> > > > would mean I would have to implement the rest of the chain my
> > > > self.
> > 
> > Seems I was missinformed/missunderstod :)
> > 
> > > IMO ctest+cdash can do at least 90% of what we need.
> > > The missing things should be added there instead of implementing an
> > > own
> > > independent solution from scratch.
> > > 
> > > The typical setup with ctest+cdash is that you set up a cronjob,
> > > which
> > > starts a continuous build at some time of the day, this cont. build
> > > job
> > > then runs for basically the whole day and checks every few minutes
> > > whether there were updates.
> > > If there were updates, it updates, builds, tests and submits the
> > > build
> > > and test results to cdash.
> > 
> > Are there any examples of what this cronjob run for command?
> 
> This is the documentation we currently have:
> http://techbase.kde.org/Development/CMake/DashboardBuilds
> 
> There it is documented for nightly builds, i.e. once per day, for continous
> builds I can send you something tomorrow.

Please do.

> Let me know if something is wrong, missing, etc.

I'm currently trying to get the nightly script working and will update the 
page with the changes I find, most notably the svn -> gti move I guess.

> > > What more do we need in your opinion ?
> > > 
> > > The missing 10% from my POV:
> > > -group result on cdash per submitting machine over multiple projects
> > > -fine grained notification emails on a subproject basis
> > 
> > Does it have IRC notification capabilities?
> 
> No.

Then this might be a good candidate for a patch :)

> > > > But I could get the xml
> > > > results from CTest I would get away with implementing the
> > > > conversion
> > > > from
> > > > CTest xml to JUnit xml as that seems to be more or less the
> > > > standard
> > > > (among the systems I've looked at).
> > > > 
> > > > Also I'm not sure if this is just a missunderstanding or
> > > > configurable
> > > > but
> > > > CDash seems to group results on a per computer basis and not on
> > > > a per
> > > > project basis.
> > > 
> > > No, it is per project. Where have you seen it per computer ?
> > 
> > In the project view.
> 
> Can you post the link please ?

http://my.cdash.org/index.php?project=kdepim

/Regards
Torgny