Closed
Bug 1042101
Opened 10 years ago
Closed 10 years ago
[Baloo] [QA] Schema update to include Moztrap
Categories
(Community Building :: Systems and Data, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pierros, Unassigned)
References
Details
(Whiteboard: [Baloo][Q3])
We need to amend Baloo schema to handle Moztrap specific data https://wiki.mozilla.org/Baloo/Schema/0.1 What fields should we add?
Comment 1•10 years ago
|
||
Here are the tables, fields, and related foreign key paths to get the info I think you'll need. email: auth_user.email result user: execution_result.created_by_id ==> auth_user result date: execution_result.created_on result to case: execution_result.runcaseversion_id ==> execution_runcaseversion case to run: execution_runcaseversion.run_id ==> execution_run run to product version: execution_run.productversion_id ==> core_productversion product version to product: core_productversion.product_id ==> core_product The result has a pretty long chain. But I think you can see how you can get information from each table in the chain. For instance: from execution_run, you can get the name of the test run, etc. But following it further down the foreign key chain, you can get to the core_product which would tell you if it's Firefox vs. Firefox OS, etc. Please ping me if you need more info on this.
Reporter | ||
Updated•10 years ago
|
Whiteboard: [Baloo]
Reporter | ||
Updated•10 years ago
|
Whiteboard: [Baloo] → [Baloo][Q3]
Reporter | ||
Comment 2•10 years ago
|
||
Schema is now updated as per comment #1 https://wiki.mozilla.org/Baloo/Schema/0.1
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•