opendev
/
puppet-openstackci
Code Issues Proposed changes
RETIRED, Puppet module to deploy an OpenStack ci system
42 Commits 1 Branch 0 Tags 2.6 MiB
Go to file
Joshua Hesketh fededacaf0 Handle all requests through os-loganalyze 
os-loganalyze now has the ability to provide indexes for both on
disk and in swift files. Handle all requests through osloganalyze
so that paths containing both disk and swift files can have all
of their assets listed.

Change-Id: I495ce20d56b04fdc5c2051f2bbcb834049ac6bda
 		2015-09-30 11:42:04 +10:00
files Set up file conditions for os-loganalyze 2015-08-11 21:36:40 +10:00
manifests Merge "Add zuul git_source_repo parameter" 2015-09-14 16:42:54 +00:00
spec Fix target path for regular git clone during tests 2015-08-19 10:39:23 +00:00
templates Handle all requests through os-loganalyze 2015-09-30 11:42:04 +10: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 Migrate to puppet-httpd module 2015-07-24 13:32:54 -04: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.