James E. Blair a5f3c1cffe Add a soft dependency between gitea build and run
When we run the run-gitea job, make sure that it runs *after*
the gitea image build job, if the build job ran at all.  If
it didn't, we don't need to worry about it.

This has to happen in the project pipeline config because the
job dependency is different in check and gate.

Change-Id: I7cb069a6cd40a4ae8d5cbcdf23e7686b301493a1
2019-03-08 15:47:50 -08:00
2019-03-05 19:51:10 +00:00
2019-02-27 11:18:04 +11:00
2019-02-14 16:39:12 -08:00
2019-03-06 15:08:17 -08:00
2019-03-08 15:44:27 -08:00
2016-07-15 12:04:48 -07:00
2018-11-02 08:19:53 +11:00
2016-06-02 10:47:36 +03:00
2019-02-13 14:52:59 -08:00
2014-09-30 12:40:59 -07:00
2018-06-25 11:19:43 +10:00
2018-06-25 11:19:43 +10:00
2019-03-06 18:42:39 +00:00

Puppet Modules

These are a set of puppet manifests and modules that are currently being used to manage the OpenStack Project infrastructure.

The main entry point is in manifests/site.pp.

In general, most of the modules here are designed to be able to be run either in agent or apply mode.

These puppet modules require puppet 2.7 or greater. Additionally, the site.pp manifest assumes the existence of hiera.

See http://docs.openstack.org/infra/system-config for more information.

Documentation

The documentation presented at http://docs.openstack.org/infra/system-config comes from git://git.openstack.org/openstack-infra/system-config repo's docs/source. To build the documentation use

$ tox -evenv python setup.py build_sphinx

Description
System configuration for the OpenDev Collaboratory
Readme 152 MiB
Languages
Python 37.1%
Jinja 36.6%
Shell 13.6%
Dockerfile 3.8%
JavaScript 3%
Other 5.9%