Open Stack

Wow, I have (almost) nothing to add.


On 10/25/2017 12:22 AM, James E. Blair wrote:
> [...]
>
> c) Add a config option to disable the implicit branch matcher
>
> There are some times when an implicit branch matcher on master may be
> undesirable.  For example when tempest was becoming branchless, it had
> multiple branches, but we would have wanted the jobs defined on master
> to be applicable everywhere.  Or if, for some reason, we wanted to
> create a feature branch on zuul-jobs.  For these cases, it's necessary
> to have an option to disable the implicit branch matcher.  We can add a
> new kind of configuration object to zuul.yaml, for example:
>
>    - meta:
>        implicit-branch-matcher: False
>
> Which would be intended only to apply to the current branch.  Or we
> could add an option to the tenant config file, so the admin can indicate
> that a certain project should not have an implicit branch matcher
> applied to certain branches.
I vote for adding this to the zuul.yaml as I think this should belong to 
the
project and not to the admin. Further this is more flexible as changes to
the tenant config requires some deployment and full zuul reload which
I think creates a potentially high process and runtime cost for changing 
this.

All of these changes sound logical to me.

Thanks for this well written excerpt :)

Tobias