opendev
/
puppet-openstackci
Code Issues Proposed changes
RETIRED, Puppet module to deploy an OpenStack ci system
70 Commits 1 Branch 0 Tags 2.6 MiB
Go to file
Evgeny Antyshev c89b2c917c Custom Jenkins vhost 
This allows the CI admin to access Jenkins
by externally resolvable name

Change-Id: I3dca0d048b5013398a3b91d9157eb3f02e5c5bb5
 		2015-12-22 13:06:42 +00:00
contrib Custom Jenkins vhost 2015-12-22 13:06:42 +00:00
files Match file conditions to apache rewrite rules 2015-10-08 10:39:52 -07:00
manifests Custom Jenkins vhost 2015-12-22 13:06:42 +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.