Re: Updated (and tested) instructions (and current issues)

[Iago Toral Quiroga <itoral igalia com>]

Hi,

I managed to make code coverage work in my machine, although I had to
made a little change to JHBuildModulePathCommand (guess due to the
buildbot upgrade).

It is still not suitable for the default configuration oughht, since it
requires the user to run a webserver to serve the code coverage reports,
but at least someone willing to do it can set it up.

Iago

El jue, 02-10-2008 a las 15:16 +0200, Iago Toral Quiroga escribió:
> Hi all,
> 
> I've been a bit overloaded for some time but I hope things will
> progressively come back to normal now (I haven't forgotten about
> buildbot :))
> 
> I'll devote a bit of time to setup and check the coverage reports today,
> hopefully I will get it done.
> 
> Iago
> 
> El jue, 14-08-2008 a las 11:14 +0200, Frederic Peters escribió:
> > Hello,
> > 
> > I got a version running on http://jhbuild.bxlug.be:8080/ so I could
> > document everything properly.
> > 
> > Configuring the master
> > 
> >   svn co http://svn.gnome.org/svn/jhbuild/trunk jhbuild
> >   cd jhbuild/
> >   make -f Makefile.plain install
> > 
> >   jhbuild bot --setup
> > 
> >   cat << _EOF_ > ~/.jhbuildrc
> >   checkoutroot = '/path/to/checkout/'
> >   prefix = '/path/to/prefix/'
> >   _EOF_
> > 
> >   jhbuild bot --start-server
> > 
> >   vi buildbot/master.cfg # to edit c['buildbotURL']
> > 
> >   cat << _EOF_ > buildbot/slaves.csv
> >   slavename,password
> >   _EOF_
> > 
> > 
> > Configuring the slave
> > 
> >   Note: my slave was an existing jhbuild instance, so all classic
> >   jhbuild stuff was already ok.
> > 
> >   Note: it is currently *not* possible to have a slave using an
> >   alternate jhbuildrc.  This means it is not possible to have
> >   several slaves sharing the same home.
> > 
> >   svn update
> > 
> >   jhbuild bot --setup
> >   cat >> _EOF_ >> ~/.jhbuildrc
> >   jhbuildbot_master = 'localhost:9070'
> >   jhbuildbot_slavename = 'slavename'
> >   jhbuildbot_password = 'password'
> >   _EOF_
> > 
> >   jhbuild bot --start
> > 
> >   There it failed with an PTY related error (perhaps because it was
> >   run in an incorrectly configured chroot?); updating the file
> >   jhbuild/commands/bot.py with usepty = 0 (instead of = 1) fixed that.
> >   Should this be the default?  (or just be made configurable?)
> > 
> > 
> > To summarize, a great success, the most important issue to fix now is
> > to get it working with slaves not using the default ~/.jhbuildrc
> > location.
> > 
> > 
> > Regards,
> >         Frederic
> > 
> > _______________________________________________
> > Build-brigade-list mailing list
> > Build-brigade-list gnome org
> > http://mail.gnome.org/mailman/listinfo/build-brigade-list
> >