Re: Announcement/RFC: jhbuild continuous integration testing
- From: Claudio Saavedra <csaavedra gnome org>
- To: desktop-devel-list gnome org
- Subject: Re: Announcement/RFC: jhbuild continuous integration testing
- Date: Tue, 12 Feb 2013 23:24:11 +0200
This is really awesome stuff!
On Tue, 2013-02-12 at 07:43 +0100, Martin Pitt wrote:
> To make this really useful, we can't rely on developers checking this
> every hour or every day, of course; instead we need push notifications
> as soon as a module starts failing. That's the bit which needs broader
> discussion and consent.
>
> I see some obvious options here what to do when the status of a module
> (OK/fails tests/fails build) changes:
>
> (1) mail the individual maintainers, as in the DOAP files
> (1a) do it for everyone, and let people who don't want this filter
> them out on a particular mail header (like "X-GNOME-QA:")
> (1b) do this as opt-in
>
> This most often reaches the people who can do something about the
> failure. Of course there are cases where it's not the module's fault, but a
> dependency changed/got broken. There is no way we can automatically
> determine whether it was e. g. a deliberate API break which modules
> need to adjust to, or indeed a bug in the depending library, so we
> might actually need to mail both the maintainers of the module that
> triggered the rebuild, and the maintainers of the module which now
> broke.
>
> (2) one big mailing list with all failures, and machine parseable
> headers for module/test
(3) Automatically filing a bug in the broken module with the details of
the breakage and additionally CC: whoever might be interested in keeping
an eye on the continuous integration?
Claudio
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]