96c6bf868a
We need a way to get the ansible playbooks onto the ansible launch servers. That's easy for jobs defined in-repo because their repo will already be on the launch server by definition. But for the tenant-global config, those playbooks (and roles, etc) need to be made available as well. Rather than shipping them around on the gearman bus which is inefficient, let's just say that those will also be in a repo. Probably the same repo that defines the jobs, ie in our case, the project-config repo. In other words -- by making the global config one or more repos that zuul knows about, the merger component of the launch server can prepare *that* repo as well as the others involved in any job, so that the playbooks are available to ansible. This also has the potential upside of making changes that Depends-On zuul configuration or ansible playbook changes much more natural to implement. We also keep track of the source repo for job definitions so that we can potentially use that to tell the launch server what repos should be included for playbooks, though this is not plumbed through yet. This adds some features to the test framework to copy a directory in the fixtures dir into a git repo since we're going to have a lot more 'git repo content' that should just be in the fixtures dir. It also removes the merge worker from the tests because it was racing with the ansible launcher cat handler. The merge worker can probably be completely removed in a later change. Change-Id: I8fc5a8f627e3d915d54d15e70b7960655a6332a1 |
||
|---|---|---|
| doc | ||
| etc | ||
| tests | ||
| tools | ||
| zuul | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| LICENSE | ||
| MANIFEST.in | ||
| NEWS.rst | ||
| README.rst | ||
| TESTING.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Zuul
Zuul is a trunk gating system developed for the OpenStack Project.
Contributing
To browse the latest code, see: https://git.openstack.org/cgit/openstack-infra/zuul/tree/ To clone the latest code, use git clone git://git.openstack.org/openstack-infra/zuul
Bugs are handled at: https://storyboard.openstack.org/#!/project/679
Code reviews are, as you might expect, handled by gerrit. The gerrit they use is http://review.openstack.org
Use git review to submit patches (after creating a gerrit account that links to your launchpad account). Example:
# Do your commits
$ git review
# Enter your username if prompted