c94c1e628c
Currently it is hard to test changes on trusted repositories. The currently most common way is to duplicate jobs and roles and have base jobs that use the test variants of the roles under test. This however still imposes a risk of breaking things when trying to move the tested changes to the productive roles and jobs. Further as a downstream deployer it can be hard to follow e.g. zuul-jobs because those are not tested in every downstream deployment. There is no easy way of updating upstream repos like zuul-jobs. Thus most deployers either just follow zuul-jobs and deal with eventual fall out from incompatibilities or don't update it on a regularly basis. This change aims to support an easier and risk free method of updating repos like zuul-jobs. This can be done by defining branch filters for a repo in the tenant config. This way one can have a test tenant using the latest is greatest master branch while keeping a stable branch for productuve tenants. This way updates can be tested in the test tenant and if everything works one can merge this to the stable branch to take the updates into production. Change-Id: Id4b5e80c0b59e4075774e6ed0049b229173e8426
7 lines
189 B
YAML
7 lines
189 B
YAML
---
|
|
features:
|
|
- |
|
|
The tenant configuration now supports loading a different branch than
|
|
master from config projects.
|
|
See :attr:`tenant.config-projects.<project>.load-branch`.
|