Re: Announcement/RFC: jhbuild continuous integration testing

[Olav Vitters <olav vitters nl>]

On Wed, Feb 13, 2013 at 06:53:17AM +0100, Martin Pitt wrote:
> Travis Reitter [2013-02-12 13:21 -0800]:
> > 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'd like to offer:
> > 
> > (0) auto-file an urgent/critical bug against the module in the case of
> > build breaks (and maybe high/major for test breaks?)
> 
> Claudio Saavedra [2013-02-12 23:24 +0200]:
> > (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?
> 
> This creates more overhead, but I like this proposal as well. I guess
> one can use python-bzutils and the like to auto-create bugs, and
> remember on the Jenkins side which bug was opened for which module,
> and auto-close it once the build works again.
> 
> The main issue that I see with this is that it's much harder to filter
> away/opt out, so it requires some broader consensus that we want to do
> this. We can still add a module blacklist if needed, though.

I think build issues should be filed as Bugzilla bugs. At most we maybe
want to set some keyword / status whiteboard. But I guess the summary
would be consistent and people will quickly learn of it.

You can use information from DOAP files to figure out the Bugzilla
product. This is not always needed. Then commit whatever DOAP fixes are
needed (the DOAP files are not bug free :P. In case someone wants to opt
out, we can add a new gnome-specific option to the DOAP file specifying
that any Continuous Integration is not welcome.

What I do in ftpadmin (see sysadmin-bin) is:
- Check if there is a bug-database with 'bugzilla.gnome.org'
  For those URL(s): Check if the URL containers product=$SOMETHING
- If there is a good product: use that
- else: assume tarball = bugzilla product (will fail for jhbuild, often
  modules are renamed and you don't know the real one)

Note: Not all products are on bugzilla.gnome.org. Maybe after GNOME
bugzilla, strive for 'bugs.freedesktop.org'?

For monitoring these bugs, you can easily watch people in Bugzilla.

-- 
Regards,
Olav