James E. Blair
4f93d6d527
The project pipelines themselves have branch matchers now, so we should not add implied branch matchers to project-pipeline job variants. This error would cause centrally defined tag/release jobs not to run when added to in-repo project-pipeline definitions in multi-branch repos because these project-pipeline variants would end up with branch matchers. There remains a similar case where if a job is defined in a multi-branch repo with no explicit branch matchers and added to a tag/release pipeline, it will not run because the job definition itself will not match the tag. Currently the only solution to this is to add an explicit branch matcher to one or more of the top-level job definitions. A more intuitive solution is difficult because in the case of multiple variants, it's not clear which should apply. Removing the implied branch matchers from project-pipeline jobs also removes them from project-template jobs. We previously added branch matchers to project configs, but did not do the same for project-templates. This change requires that we do so. Now all projects and project-templates are given implied branch matchers if appropriate, and these are used to determine if their jobs are added. This is a further behavior change in that a project which invokes a template defined in another project which is branched will (absent the disabling of implicit branch matchers) no longer use that template on branches other than the one where it is defined. Change-Id: I55cec1897b0d64fa61d43ef5dbeb8a3c37bf7862
Zuul
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
If you are looking for the Javascript testing tool named Zuul, it 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 in the #zuul channel on Freenode IRC.
Contributing
To browse the latest code, see: https://git.zuul-ci.org/cgit/zuul/tree/ To clone the latest code, use git clone https://git.zuul-ci.org/zuul
Bugs are handled at: https://storyboard.openstack.org/#!/project/679
Code reviews are handled by gerrit at https://review.openstack.org
After creating a Gerrit account, use git review to submit patches. Example:
# Do your commits
$ git review
# Enter your username if promptedJoin #zuul on Freenode 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 v3 requires Python 3. It does not support Python 2.
As Ansible is used for the execution of jobs, it's important to note
that while Ansible does support Python 3, not all of Ansible's modules
do. Zuul currently sets ansible_python_interpreter to
python2 so that remote content will be executed with Python 2.