A few questions for each tool

[Gonéri Le Bouder]

On Mon, Sep 01, 2008 at 09:42:29PM +0200, Lucas Nussbaum wrote:
> Hi,
Hi folks,

> Please try to answer those questions.
> 
> - Define the goal of your tool in one line (i.e which problem is it
>   trying to solve?)
buildstat have two goals:
 -To give the state of list of packages from different origins:
  + Debian repository
  + svn
  + git
 -Give a easy to store result of QA tools like lintian, build or
 gcc-snapshot build, .desktop checks etc
> - Where is the code? Where does it run, currently?
The code is on collab-qa SVN.
http://svn.debian.org/wsvn/collab-qa/buildstat/?rev=0&sc=0

I rant 2 machines for them and I can of course provide access to them.

> - Which URL do users use to access it? Provide one/a few pages as
>   example.
http://svnbuildstat.debian.net (stable)
http://buildstat.debian.net (futur release)

This page may work:
http://buildstat.debian.net/packages/list/pkg-games-devel@lists.alioth.debian.org
Note the "main ( apt )" and "Debian Games Team ( svn )" links.

> - Which languages did you use ?
Perl with:
 - Catalyst
   http://www.catalystframework.org/
 - DBIx::Class, mostly in the scripts
   http://search.cpan.org/dist/DBIx-Class/lib/DBIx/Class/Manual/Example.pod 
 - TemplateToolkit2 http://template-toolkit.org/

> - How do you store data? (think of all the data you use, including a
>   local mirror, local checkouts from svn, etc). Can you describe its
>   schema, or point to a schema somewhere?
DB and local cache directories for VCSes.
The graphic DB schema:
http://nana.rulezlan.org/~goneri/svnbuildstat_devel_db_schema.png

The autodoc documentation
http://nana.rulezlan.org/~goneri/buildstat/buildstat.html

The SQL file:
http://svn.debian.org/wsvn/collab-qa/buildstat/trunk/buildstat-server/schema-pg.sql?op=file&rev=0&sc=0

I do a local checkout of the VCS repositories and store some files like
build result or log files.

> - Which data from external sources do you use? How do you update it?
BTS throught its LDAP dump:
http://qa.debian.org/data/bts2ldap/fullindex

watch file with uscan

Debian FTP:
I fetch the Sources.gz, it's possible to add mentors.d.n but IMO we will
have security problem if we want to rebuild the packages.

VCS repositories:
adding new VCS like bzr is trivial

The scripts are in this directory on the svn:
http://svn.debian.org/wsvn/collab-qa/buildstat/trunk/buildstat-server/script/?rev=0&sc=0

external QA jobs and build results:
They are received by Apache to pass through the HTTP proxies and
processed by a script.

I also query rmadison but will be able to stop soon.

Scripts are launched by cron.

> - Which data do you generate locally? (using tests, for example?)
None and it's not the goal of the architecture.
 
> - Which questions did I forget?
buildstat is uncentralized. Easily, ones can use it to have there own script result
displayed on the proper package page (e.g: a Sparc rebuild campaign).

Cheers,

    Gonéri Le Bouder
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pet-devel/attachments/20080901/452c6b21/attachment.pgp