Go to file

Allow nodepool to launch 3 process, instead of 1. This is to overcome
capacity issues with a single process.

Change-Id: Ibe41ce3c488da9cd68d8833b61fd42682f0b4e73
Depends-On: Iaee3148d6710f796e9f1ea7cba2962cfbb530fa2
Signed-off-by: Paul Belanger <pabelanger@redhat.com>

2016-10-05 17:26:46 -04:00

contrib

Merge "Custom Jenkins vhost"

2016-08-18 08:52:27 +00:00

doc/source

set up a git repo add set account's default identity

2016-06-22 22:13:09 -04:00

files

Match file conditions to apache rewrite rules

2015-10-08 10:39:52 -07:00

manifests

Add split daemon support for nodepool

2016-10-05 17:26:46 -04:00

spec

Use openstack-infra jenkins users public ssh key

2016-06-09 13:35:45 -04:00

templates

Logs: serve .log and .sh files as text/plain

2016-06-15 10:48:27 -07: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.