Confirmed users
353
edits
EngineeringProductivity/Projects/Treeherder: Difference between revisions
Jump to navigation
Jump to search
EngineeringProductivity/Projects/Treeherder (view source)
Revision as of 02:21, 21 December 2012
, 21 December 2012→Revaluation of the Data Model
| Line 61: | Line 61: | ||
** Example attributes: A branch has a version attribute, A build has a log attribute | ** Example attributes: A branch has a version attribute, A build has a log attribute | ||
** Do we have that represented in the existing TBPL database schema + hard coded javascript? | ** Do we have that represented in the existing TBPL database schema + hard coded javascript? | ||
* Determine at what point in the life cycle of a build or push that data is available for all entities/attributes for all products (Firefox, Fennec, Firefox OS etc...). So this part would be the idiosyncratic/messy part, the answer could be different for a product using mercurial vs git or Buildbot vs WhateverBuild thingy is being used and that's why we need it encapsulated. | * Determine at what point in the life cycle of a build or push that data is available for all entities/attributes for all products (Firefox, Fennec, Firefox OS etc...). So this part would be the idiosyncratic/messy part, the answer could be different for a product using mercurial vs git or Buildbot vs WhateverBuild thingy is being used and that's why we need it encapsulated. | ||