Open Stack

On Tue, May 30, 2017 at 4:55 AM, Jeremy Stanley <fungi at yuggoth.org> wrote:

> On 2017-05-29 13:34:47 +1000 (+1000), Joshua Hesketh wrote:
> [...]
> > We could extend the 'start message' of zuul to explain what it is
> > about to do. eg: "Testing change XYZ against $branch, with change
> > XYZ applied to $project $branch, with..." etc.
>
> This would be hard (I think for definitions of hard roughly equal to
> impossible) for dependent pipelines since the non-declared
> dependencies which will be tested in the pile can't be guessed in
> advance (some may be kicked out, some may come between declared
> dependencies, et cetera).
>

Right you are. Unless the start message is reposted each time the
dependencies are recalculated this isn't the best place.


>
> > This could alternatively go into a "state" file (of sorts) in the
> > zuul logs/output. ie, summarise what the zuul-cloner did into
> > simple terms that doesn't involve large logs.
>
> I'm assuming you mean zuul-merger unless zuul-cloner is growing to
> replace zuul-merger in v3 or something? Anyway, I agree a general
> logset per changeish might be nice in addition to per-job logs and
> this information might fit well somewhere there (or copied into each
> build result).
>

Right, merger or cloner (since the cloner gets what the merger prepped).

Cheers,
Josh


> --
> Jeremy Stanley
>
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20170530/75a660f7/attachment.html>