Go to file

Doug Wiegley beca1bbbe7 Do initial git commit with stock puppet files

So that later config changes are tracked separately.

Change-Id: Ic3a6485254b96cdc5624aa349e027f99f2e8d6c1

2015-12-22 17:13:16 -07:00

contrib

Do initial git commit with stock puppet files

2015-12-22 17:13:16 -07:00

files

Match file conditions to apache rewrite rules

2015-10-08 10:39:52 -07:00

manifests

Merge "Allow logserver to run on CI server (part 2)"

2015-12-21 18:22:38 +00:00

spec

Fix target path for regular git clone during tests

2015-08-19 10:39:23 +00:00

templates

Prepopulate log server for single-node-ci

2015-11-20 09:48:39 -08:00

.gitreview

Added .gitreview

2015-03-18 17:00:55 +00:00

Gemfile

Add Gemfile

2015-06-08 12:41:18 -07:00

LICENSE

Initial files for the puppet-openstackci repo

2015-03-24 12:05:27 -07:00

metadata.json

Add generic logstash manifests

2015-10-28 13:19:43 -05:00

Rakefile

Initial files for the puppet-openstackci repo

2015-03-24 12:05:27 -07:00

README.md

Add developer guidelines

2015-04-29 01:46:24 -07:00

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.