opendev
/
puppet-openstackci
Code Issues Proposed changes
RETIRED, Puppet module to deploy an OpenStack ci system
65 Commits 1 Branch 0 Tags 2.6 MiB
Go to file
Dan Moravec 670300f842 Clarifications to the getting started notes in contrib/README 
The existing notes were very easy to follow. I especially appreciated the
step-by-step flow and inclusion of commands to run. As I followed the
documentation, I found a couple of typos and added a few clarifications.

Change-Id: I604679f70c2474a440befa44af15ac3cc6d18c08
 		2015-12-04 09:49:01 -06:00
contrib Clarifications to the getting started notes in contrib/README 2015-12-04 09:49:01 -06:00
files Match file conditions to apache rewrite rules 2015-10-08 10:39:52 -07:00
manifests Merge "Ensure build-essential and python-dev are installed" 2015-12-01 18:12:55 +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
README.md Add developer guidelines 2015-04-29 01:46:24 -07:00
Rakefile 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

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.