388a2767df
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have. |
||
---|---|---|
contrib | ||
doc/source | ||
files | ||
manifests | ||
spec/acceptance | ||
templates | ||
.gitignore | ||
.gitreview | ||
CONTRIBUTING.rst | ||
Gemfile | ||
LICENSE | ||
README.md | ||
Rakefile | ||
bindep.txt | ||
metadata.json | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.md
OpenStack Continuous Integration Module
Overview
Configures an OpenStack Continuous Integration System
Developing
If you are adding features to this module, first ask yourself: "Does this logic belong in the module for the service?"
An example of this is the gearman-logging.conf file needed by the zuul service. This file should be managed by the zuul module, not managed here. What should go in this module is high level directives and integrations such as a list of jenkins plugins to install or a class that instantiates multiple services.