James E. Blair
b72800266c
This change switches out the unparsed config cache in favor of a new config object cache which holds parsed config objects. These objects are used in all tenants, and when a tenant is reconfigured, only the objects from the changed files are replaced in the cache. When a layout is created, it is assembled from the relevant objects in the cache (filtering for the various settings on the tenant project config). The rough overview of configloader caching is now: * File cache (serialized json in ZK, populated from merger cat jobs) * Config object cache (python objects in memory) None of which have any tenant-specific information. This does make one intentional behavioral change: the load-classes for trusted and untrusted projects are currently identical except that untrusted projects are not configured to load pipelines. The sequence of events when creating a static and dynamic layout is slightly different, and the load-classes end up filtering pipelines out from untrusted projects before we check for them and add the PipelineNotPermitted configuratione error. But in the dynamic path, we check for that error first. Because both code paths are much closer in behavior with this change, we need to resolve this discrepancy. In this change, it is resolved in favor of adding the configuration error to the static code path. That means that the load-classes for trusted and untrusted projects are the same, and we rely solely on the check in addProjectBranchConfig to either add the pipeline or add the error. This method is called in both the static and dynamic paths. Change-Id: I6a63848f8478ed087ae493981fd1dc81dfff842d
Zuul
Zuul is a project gating system.
The latest documentation for the current version of Zuul is published at: https://zuul-ci.org/docs/zuul/
If you are looking for the Edge routing service named Zuul that is related to Netflix, it can be found here: https://github.com/Netflix/zuul
If you are looking for the Javascript testing tool named Zuul, its archive can be found here: https://github.com/defunctzombie/zuul
Getting Help
There are two Zuul-related mailing lists:
- zuul-announce
-
A low-traffic announcement-only list to which every Zuul operator or power-user should subscribe.
- zuul-discuss
-
General discussion about Zuul, including questions about how to use it, and future development.
You will also find Zuul developers on Matrix <https://matrix.to/#/#zuul:opendev.org>.
Contributing
To browse the latest code, see: https://opendev.org/zuul/zuul To clone the latest code, use git clone https://opendev.org/zuul/zuul
Bugs are handled at: https://storyboard.openstack.org/#!/project/zuul/zuul
Suspected security vulnerabilities are most appreciated if first reported privately following any of the supported mechanisms described at https://zuul-ci.org/docs/zuul/latest/vulnerabilities.html
Code reviews are handled by gerrit at https://review.opendev.org
After creating a Gerrit account, use git review to submit patches. Example:
# Do your commits
$ git review
# Enter your username if promptedJoin us on Matrix to discuss development or usage.
License
Zuul is free software. Most of Zuul is licensed under the Apache License, version 2.0. Some parts of Zuul are licensed under the General Public License, version 3.0. Please see the license headers at the tops of individual source files.
Python Version Support
Zuul requires Python 3. It does not support Python 2.
Since Zuul uses Ansible to drive CI jobs, Zuul can run tests anywhere Ansible can, including Python 2 environments.