Go to file

Jeremy Stanley 5cc230c4f2 Clean up elasticsearch cleanup cronjob

The old cronjob to delete Elasticsearch indices has been unused and
set absent for a while. Recent changes in Puppet seem to have
started disliking the literal \% sequences in the string, so just go
ahead and remove it.

Change-Id: Ic81ac00935bc3f79f17371ef13ad4d1686ffb028

2017-05-25 22:58:30 +00:00

contrib

Pass Java arguments to Jenkins master

2017-03-28 10:41:38 +03:00

doc/source

Remove link to modindex

2016-12-28 16:43:04 +01:00

files

Reduce job log retention to 45 days

2017-02-15 21:21:43 +00:00

manifests

Clean up elasticsearch cleanup cronjob

2017-05-25 22:58:30 +00:00

spec

Fix beaker-rspec tests for centos7

2017-04-13 22:37:52 +02:00

templates

Allow logs.o.o to server gzipped svg files

2017-03-03 09:14:01 -05:00

.gitignore

Initial sphynx doc setup for publishing

2016-01-04 14:51:15 -08:00

.gitreview

Added .gitreview

2015-03-18 17:00:55 +00:00

bindep.txt

Move other-requirements.txt to bindep.txt

2016-08-12 19:30:33 +02:00

CONTRIBUTING.rst

Add a CONTRIBUTING.rst document

2016-01-07 17:34:58 -08:00

Gemfile

Use new infra_spec_helper for gem dependencies

2016-06-21 17:57:36 -07:00

LICENSE

Initial files for the puppet-openstackci repo

2015-03-24 12:05:27 -07:00

metadata.json

Use our custom pip provider for keyring package

2016-04-22 09:25:49 -07:00

Rakefile

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

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.