Matthew Treinish 10e5d0eda5 Bump oslo.config version
There is a bug in oslo.config <=1.3.0 when registering cli opts with
deprecated_opts set. This causes an error with registering the oslo.db
opts. The bug was fixed post 1.3.0, so pinning this to >= the latest
alpha, which will pull in any release 1.4.0 when it becomes available.

Closes-Bug: #1347911

Change-Id: I58505ffcdfb0acf0ed2137282c18258e94e201f6
2014-07-23 22:53:16 +00:00
2014-06-24 16:21:38 -04:00
2014-06-24 15:50:36 -04:00
2014-07-12 12:48:23 -04:00
2014-06-24 20:14:18 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-24 16:00:13 -04:00
2014-07-23 22:53:16 +00:00
2014-07-06 14:27:34 -04:00
2014-06-12 23:59:00 -04:00
2014-07-09 15:55:41 -04:00
2014-06-24 20:14:18 -04:00

subunit2SQL README

subunit2SQL like it's name implies is a tool used for converting subunit streams to data in a SQL database. The motivation is that for multiple distributed test runs that are generating subunit output it is useful to store the results in a unified repository. This is the motivation for the testrepository project which does a good job for centralizing the results from multiple test runs.

However, imagine something like the OpenStack CI system where the same basic test suite is normally run several hundreds of times a day. To provide useful introspection on the data from those runs and to build trends over time the test results need to be stored in a format that allows for easy querying. Using a SQL database makes a lot of sense for doing this.

subunit2SQL uses alembic migrations to setup a DB schema that can then be used by the subunit2sql binary to parse subunit streams and populate the DB. Additionally, it provides a DB API that can be used to query information from the results stored to build other tooling.

Description
Tooling for converting subunit streams into a SQL DB
Readme 6.1 MiB
Languages
Python 99.4%
Shell 0.5%
Mako 0.1%