opendev
/
puppet-openstackci
Code Issues Proposed changes
RETIRED, Puppet module to deploy an OpenStack ci system
3 Commits 1 Branch 0 Tags 2.6 MiB
Go to file
Spencer Krum 09f33fb5df Add developer guidelines 
Change-Id: Idf04135bb8037fdc3e9cb6e65e53654524abfabf
 		2015-04-29 01:46:24 -07:00
.gitreview Added .gitreview 2015-03-18 17:00:55 +00: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 Initial files for the puppet-openstackci repo 2015-03-24 12:05:27 -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.