Open Stack

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 to treat builds as effectively canceled if there
is no corresponding gearman worker, this would avoid the
not_registered comment in all cases. This can be done in one line of
code if you just hack it [1] (assuming my patch is correct).

 - Automatically register all jobs that zuul tries to start with
gearman. That is, check if <job-foo> exists on gearman, and register
dummy function if not, for each attempted build. This would avoid
missing any patches.

[1] https://review.openstack.org/#q,Ie6d5ea35c6eeed465168f24921b04442df8f5744,n,z


On Mon, Aug 1, 2016 at 10:53 AM, Lenny Verkhovsky <lennyb at mellanox.com> 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 not commenting in such cases at all as discussed
> in [2].
>
>
>
> If a developer is missing some important CI comments, it can rechecked later
> or sent an email to CI owner.
>
>
>
> [1] No valid slaves
>
>        Not all jobs are registered due to zuul restart for instance
>
>
>
> [2]
> http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2016-08-01.log.html
>
>
>
>
>
> Thanks.
>
> Lenny
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>