On GitHub we cannot reliably update all information that's needed for doing a canmerge check using events. Namely completely missing events on branch protection changes and ambiguous status events that might match several changes due to its data model to have statuses on the commit instead the pr. This was no problem in the past since this information was only used during the enqueue phase which is directly after the event preprocessing phase. However with circular dependencies we re-do the can merge check just before merging again and need to act on recent data. Therefore add an allow_refresh flag that makes it possible to refresh the volatile parts of the data we don't get events for. This is only used on GitHub for now as the other drivers are either correctly updating their states using events or didn't yet optimize to not do api calls within the main loop yet (pagure). Change-Id: I89ff158642fe32c5004ef62c2e25399110564252
|8 months ago|
|doc||5 months ago|
|etc||2 years ago|
|playbooks||5 months ago|
|releasenotes/notes||5 months ago|
|tests||5 months ago|
|tools||5 months ago|
|web||5 months ago|
|zuul||5 months ago|
|.coveragerc||3 years ago|
|.dockerignore||3 years ago|
|.gitignore||1 year ago|
|.gitreview||2 years ago|
|.mailmap||9 years ago|
|.stestr.conf||3 years ago|
|.zuul.yaml||5 months ago|
|COPYING||3 years ago|
|Dockerfile||5 months ago|
|LICENSE||9 years ago|
|MANIFEST.in||1 year ago|
|README.rst||2 years ago|
|TESTING.rst||2 years ago|
|bindep.txt||10 months ago|
|reno.yaml||1 year ago|
|requirements.txt||6 months ago|
|setup.cfg||5 months ago|
|setup.py||8 years ago|
|test-requirements.txt||1 year ago|
|tox.ini||8 months ago|
Zuul is a project gating system.
The latest documentation for Zuul v3 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
There are two Zuul-related mailing lists:
A low-traffic announcement-only list to which every Zuul operator or power-user should subscribe.
General discussion about Zuul, including questions about how to use it, and future development.
You will also find Zuul developers in the #zuul channel on Freenode IRC.
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/user/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 prompted
Join #zuul on Freenode to discuss development or usage.
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.