Open Stack

On Sun, Jul 01, 2012 at 08:40:36AM -0700, James E. Blair wrote:
[snip]

> So with all that background, I think we should discuss the following at
> the CI team meeting on Tuesday:

[snip]

> 3) Decide on a course of action to mitigate failures from transient
> gerrit errors (but continue to work on eliminating them in the first
> place).
> 
> 4) Decide how to implement retriggering with Zuul.

Can you expand on what you mean by this 4th point ? Is this a way to
allow individual patch submitters to re-trigger builds on their own
patches ?

IIUC, currently only core reviewers can directly retrigger builds. It
seems patch submitters are working around this restriction by simply
doing no-op rebases & re-uploading their patches again and again until
Jenkins passes.  If there's an easy way to allow re-triggering of failed
builds by any any reviewer, it seems that would mitigate the pain of
these failures, because we won't have to rely on a small pool of
people to notice bogus failures.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|