From Fedora Project Wiki
(fix some links (some still broken)) |
|||
| Line 14: | Line 14: | ||
The project is split into these parts: | The project is split into these parts: | ||
* ResultsDB core <https://bitbucket.org/fedoraqa/resultsdb>, which is the implementation of the datastore, and the API provider. | * ResultsDB core <https://bitbucket.org/fedoraqa/resultsdb>, which is the implementation of the datastore, and the API provider. | ||
* ResultsDB Client Library <https://bitbucket.org/fedoraqa/resultsdb_api> providing the easy-to-use python implementation of the ResultsDB API, described here <http://docs.resultsdb.apiary.io/> | * ResultsDB Client Library <https://bitbucket.org/fedoraqa/resultsdb_api> providing the easy-to-use python implementation of the ResultsDB API, described here <http://docs.resultsdb.apiary.io/> | ||
* ResultsDB Frontend <https://bitbucket.org/fedoraqa/resultsdb_frontend> - a simple frontend intended for browsing the results via web interface. | * ResultsDB Frontend <https://bitbucket.org/fedoraqa/resultsdb_frontend> - a simple frontend intended for browsing the results via web interface. | ||
[[Category:ResultsDB]] | [[Category:ResultsDB]] | ||
Revision as of 13:22, 25 June 2014
What is ResultsDB
ResultsDB is a system designed to hold the results of tests executed by the Taskotron framework.
ResultsDB is only a system for storing test results, different 'frontend' apps can be created using ResultsDB as a data source. These frontends could be anything from a simple tool aggregating recent results for builds, or anything more complicated like a tool for gathering test-related metrics (historical fail/pass ratio of a specific test in a Fedora release, failure rate of critpath packages etc.).
Current state
At the moment, there are two versions of ResultsDB.
- Legacy version - first incarnation of ResultsDB, still required for tools like TestDays App, or AutoQA <https://fedorahosted.org/ResultsDB/>.
- Current development version - intender for the Taskotron project. Reimplemented to provide JSON/RESTful api, and quite slimmed down, in order to remove the relics from the primary draught.
Current development version
The project is split into these parts:
- ResultsDB core <https://bitbucket.org/fedoraqa/resultsdb>, which is the implementation of the datastore, and the API provider.
- ResultsDB Client Library <https://bitbucket.org/fedoraqa/resultsdb_api> providing the easy-to-use python implementation of the ResultsDB API, described here <http://docs.resultsdb.apiary.io/>
- ResultsDB Frontend <https://bitbucket.org/fedoraqa/resultsdb_frontend> - a simple frontend intended for browsing the results via web interface.