9e6bfded56
This adds an option to specify that certain branches should always trigger dynamic configuration and never be included in static configuration. The use case is a large number of rarely used feature branches, where developers would still like to be able to run pre-merge check jobs, and alter those jobs on request, but otherwise not have the configuration clogged up with hundreds of generally unused job variants. Change-Id: I60ed7a572d66a20a2ee014f72da3cb7132a550da
11 lines
415 B
YAML
11 lines
415 B
YAML
---
|
|
features:
|
|
- |
|
|
Added a new
|
|
:attr:`tenant.untrusted-projects.<project>.always-dynamic-branches`
|
|
tenant project configuration option. This may be used to specify
|
|
branches from which Zuul should never load static configuration
|
|
and instead treat every change as if it newly proposed dynamic
|
|
configuration. This is potentially useful for large numbers of
|
|
rarely-used feature branches.
|