On Mon, Aug 01, 2016 at 03:53:12PM +, Lenny Verkhovsky wrote:
> Hi,
>
> Currently in some cases[1] CI sets a comment on the patch set as
> NOT_REGISTERED.
>
> Those comments are very hard to monitor for CI operators and have noisy value
> for the developers.
>
> Maybe a better solution is
Thanks starting the discussion, Lenny. I thought about a way to
accomplish that, and came up with few options:
- Pre-register all possible jenkins jobs with gearman. This only
avoids not registered errors due to gearman server restart, not if you
misconfigured your system;
- Add option to zuul
Hi,
Currently in some cases[1] CI sets a comment on the patch set as NOT_REGISTERED.
Those comments are very hard to monitor for CI operators and have noisy value
for the developers.
Maybe a better solution is not commenting in such cases at all as discussed in
[2].
If a developer is missing
