opendev/subunit2sql
Code Issues Proposed changes
Tooling for converting subunit streams into a SQL DB
1 Commit 1 Branch 31 Tags 6.1 MiB
Python 99.4%
Shell 0.5%
Mako 0.1%
9d86270fac
Go to file
Matthew Treinish 9d86270fac Initial commit 
This just adds the basic framework for all the various pieces. The
schema will be built using alembic. Everything else is untested.
2014-06-12 23:59:00 -04:00
subunit2sql Initial commit 2014-06-12 23:59:00 -04:00
.gitignore Initial commit 2014-06-12 23:59:00 -04:00
alembic.ini Initial commit 2014-06-12 23:59:00 -04:00
LICENSE Initial commit 2014-06-12 23:59:00 -04:00
openstack-common.conf Initial commit 2014-06-12 23:59:00 -04:00
README.rst Initial commit 2014-06-12 23:59:00 -04:00
requirements.txt Initial commit 2014-06-12 23:59:00 -04:00
setup.cfg Initial commit 2014-06-12 23:59:00 -04:00
setup.py Initial commit 2014-06-12 23:59:00 -04:00
test-requirements.txt Initial commit 2014-06-12 23:59:00 -04:00
tox.ini Initial commit 2014-06-12 23:59:00 -04:00

README.rst

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.

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. SQL databases make 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. Additional it provides a DB API that can be used to query information from the results stored to build other tooling.