Dan Smith 1d6ae7dd83 Check the number of tests that were run after tox before success
This adds a dirty check of the output file after a tox run to make
sure that at least one test passed. If not, then we shouldn't
allow a successful result. This is intended to catch the case where
none of the tests run because of some parse or test setup error,
which might otherwise be considered a successful run.

Change-Id: I598262f47971e238876b38416c00a70de8313543
Reviewed-on: https://review.openstack.org/14402
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
2012-10-13 16:06:23 +00:00
2012-10-05 23:27:31 +00:00
2012-10-12 21:42:28 +00:00
2011-10-20 13:37:04 -04:00
2012-10-09 16:49:28 +00:00
2012-07-20 16:27:52 -07:00
2012-09-22 17:32:02 +00:00
2012-09-10 15:58:27 +00:00

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

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

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://ci.openstack.org for more information.

Description
System configuration for the OpenDev Collaboratory
Readme 154 MiB
Languages
Jinja 37%
Python 36.7%
Shell 13.6%
Dockerfile 3.9%
JavaScript 3%
Other 5.8%