Go to file

Jerry Zhao 77826301f0 fix the default gerrit_ssh_host_key

update the default gerrit_ssh_host_key to the current value that
review.o.o is using. otherwise, zuul-merger will fail to clone
git repos from gerrit because correct review.o.o host key is not
in zuul user's known_hosts.

Change-Id: I0e2ec0e340d63666de2ce0ed72c1043be0ed0662

2016-11-29 12:39:09 -08:00

contrib

fix the default gerrit_ssh_host_key

2016-11-29 12:39:09 -08:00

doc/source

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

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

files

Reduce job log retention to 60 days

2016-09-29 15:53:41 +00:00

manifests

fix the default gerrit_ssh_host_key

2016-11-29 12:39:09 -08:00

spec

Use openstack-infra jenkins users public ssh key

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

templates

Merge "Order periodic job results by date"

2016-11-14 23:58:53 +00: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.