Confirmed users
353
edits
EngineeringProductivity/Projects/Treeherder: Difference between revisions
EngineeringProductivity/Projects/Treeherder (view source)
Revision as of 02:58, 21 December 2012
, 21 December 2012→Requirements
| Line 36: | Line 36: | ||
== Requirements == | == Requirements == | ||
* The complete data model for test runs, test results, and star data would be defined by the DB, and would be consumed by TBPL | * The complete data model for test runs, test results, and star data would be defined by the DB, and would be consumed by TBPL | ||
* There would be a single set of OS/platform/test names in the DB that would be used by TBPL and any other tool that wanted to interface with it (probably including buildbot) | * There would be a single set of OS/platform/test names in the DB that would be used by TBPL and any other tool that wanted to interface with it (probably including buildbot) | ||
* There would be a well-defined, web-accessible interface for reading/writing data from the DB. | * There would be a well-defined, web-accessible interface for reading/writing data from the DB. | ||
* Log files would be parsed exactly once and the resulting data stored in the DB. | * Log files would be parsed exactly once and the resulting data stored in the DB. | ||
* TBPL would work with git-based commits and mercurial. | * TBPL would work with git-based commits and mercurial. | ||
* Adding a new tree or a new test type to TBPL would simply be a matter of writing appropriate data to the DB using interfaces designed for this; TBPL would automatically pick this up and render it. It wouldn't be necessary to tweak constants in a JS file and then file an IT bug to deploy the changes. | |||
* Adding a new tree or a new test type to TBPL would simply be a matter of writing | |||
appropriate data to the DB using interfaces designed for this; TBPL would automatically pick this up and render it. It wouldn't be necessary to tweak constants in a JS file and then file an IT bug to deploy the changes. | |||
* TBPL Must support intermittently run tests. | * TBPL Must support intermittently run tests. | ||
* TBPL and orange factor functionality should continue to merge together. | * TBPL and orange factor functionality should continue to merge together. | ||
* The UI should not be thrown out, but should be reviewed closely for expansion/drill down points. | * The UI should not be thrown out, but should be reviewed closely for expansion/drill down points. | ||
* Extend the UI with a better set of filters like the "unstarred view" that TBPL has, but cutting it down to a specific test type on a tree. | * Extend the UI with a better set of filters like the "unstarred view" that TBPL has, but cutting it down to a specific test type on a tree. | ||