opendev
/
puppet-openstackci
Code Issues Proposed changes
RETIRED, Puppet module to deploy an OpenStack ci system
222 Commits 1 Branch 0 Tags 2.6 MiB
Go to file
Andreas Jaeger f494aa8762 Handle robots.txt on logs.o.o 
We don't want to delete the top-level robots.txt file - but everything
that is part of the logs hierarchy.

Change-Id: I369565a780eb749eab95e4bf8e7d8d7fd5bf0630
 		2019-08-07 14:04:57 +00:00
contrib Add support for installing ARA wsgi middleware for sqlite databases 2018-03-05 15:08:40 -05:00
doc/source Merge "added Single Use Slave plugin" 2017-06-05 15:27:06 +00:00
files Handle robots.txt on logs.o.o 2019-08-07 14:04:57 +00:00
manifests Pin ara at 0.16.5 for logserver 2019-06-14 18:44:12 +00:00
spec/acceptance Remove idempotency spec checks 2019-05-24 08:40:38 -07:00
templates The logs for a job my contain dotfiles, index them 2019-05-23 09:31:35 -07:00
.gitignore Initial sphynx doc setup for publishing 2016-01-04 14:51:15 -08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:26:00 +00:00
CONTRIBUTING.rst Add a CONTRIBUTING.rst document 2016-01-07 17:34:58 -08:00
Gemfile Fix opendev paths 2019-04-20 15:26:42 +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
bindep.txt Add beaker-rspec bindep dependencies 2018-06-28 08:13:31 +00:00
metadata.json Fix opendev paths 2019-04-20 15:26:42 +00:00
setup.cfg Initial sphynx doc setup for publishing 2016-01-04 14:51:15 -08:00
setup.py Initial sphynx doc setup for publishing 2016-01-04 14:51:15 -08:00
test-requirements.txt Initial sphynx doc setup for publishing 2016-01-04 14:51:15 -08:00
tox.ini Initial sphynx doc setup for publishing 2016-01-04 14:51:15 -08: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.