[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: checking buildd logs

Dear DSA,

On Sun, Jun 03, 2012 at 08:47:32AM +0200, Bernhard R. Link wrote:
> > This should either be moved into
> > buildd.debian.org or qa.debian.org.  I'd personally prefer the latter,
> > but I'd understand that rsync'ing either the result or the logs might be
> > painful.  At least the latter would create more I/O load than the
> > existing setup.
> The data gathering part and the html generation are now totally
> seperated. The first updates a sqlite database file with results
> and the later used that files. So the total I/O for having those
> two parts on different machines would be transfering a file
> compressed around 7 MB (uncompressed around 30 MB) per update
> (and some way to know when new results are available).
> > I wouldn't mind if the qa role account is exported to
> > grieg.
> It would be nice if the data aquisition part would run in some role
> account once it is finished. Some qa role account sounds like the
> ideal choice. (Though I currently do not have access to that one
> as far as I know).

Bernhard is doing buildd log scanning for potential issues (see [0]). This
would not be a buildd.d.o service, but rather a qa service. Who's in charge of
the qa role account and would need to authorise that?

I presume it would mean exporting the qa role account to grieg, granting brlink
access to it, getting someone to add appropriate SSH public keys to quantz,
rsync over the database and do the HTML generation on quantz. Does that sound

Kind regards
Philipp Kern

[0] https://buildd.debian.org/~brlink/ 

Attachment: signature.asc
Description: Digital signature

Reply to: