Puppet module to deploy an OpenStack ci system
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Monty Taylor 05d6bd00bf Fix opendev paths 4 days ago
contrib Add support for installing ARA wsgi middleware for sqlite databases 1 year ago
doc/source Merge "added Single Use Slave plugin" 1 year ago
files Allow viewing of .log.gz files 1 year ago
manifests Use mod_expires to set cache headers for log files 2 weeks ago
spec/acceptance Fix opendev paths 4 days ago
templates Use mod_expires to set cache headers for log files 2 weeks ago
.gitignore Initial sphynx doc setup for publishing 3 years ago
.gitreview OpenDev Migration Patch 5 days ago
CONTRIBUTING.rst Add a CONTRIBUTING.rst document 3 years ago
Gemfile Fix opendev paths 4 days ago
LICENSE Initial files for the puppet-openstackci repo 4 years ago
README.md Add developer guidelines 4 years ago
Rakefile Initial files for the puppet-openstackci repo 4 years ago
bindep.txt Add beaker-rspec bindep dependencies 10 months ago
metadata.json Fix opendev paths 4 days ago
setup.cfg Initial sphynx doc setup for publishing 3 years ago
setup.py Initial sphynx doc setup for publishing 3 years ago
test-requirements.txt Initial sphynx doc setup for publishing 3 years ago
tox.ini Initial sphynx doc setup for publishing 3 years ago

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.