Confirmed users
353
edits
EngineeringProductivity/Projects/Treeherder/Meetings/2013-01-23: Difference between revisions
Jump to navigation
Jump to search
EngineeringProductivity/Projects/Treeherder/Meetings/2013-01-23 (view source)
Revision as of 23:00, 29 January 2013
, 29 January 2013→Design Notes
| Line 1: | Line 1: | ||
= Design Notes = | = Design Notes = | ||
* https://etherpad.mozilla.org/MyhQ3VxUHC from the meeting | *[https://etherpad.mozilla.org/MyhQ3VxUHC etherpad] from the meeting | ||
== Build Objects == | == Build Objects == | ||
* Define build base object | * Define build base object | ||
| Line 6: | Line 6: | ||
** One option for flexibility would be to have a object store that accepts more attributes that aren't on all objects (the set of required attributes would be small) -- similar to what we did with datazilla. The index of the attributes could be project specific. | ** One option for flexibility would be to have a object store that accepts more attributes that aren't on all objects (the set of required attributes would be small) -- similar to what we did with datazilla. The index of the attributes could be project specific. | ||
** There will be a core set of attributes that all objects have to have but the specifics will differ among various projects. | ** There will be a core set of attributes that all objects have to have but the specifics will differ among various projects. | ||
** Could put a proxy inside the build network so that the build system would not have to use auth to talk to this tool but things outside the build network would. The proxy could implement OAuth for the build network to simplify things. | |||
== Test Objects == | |||
* Will go up to an object store as well and then datazilla/orangefactor/graphserver will query this. This will also break the synchonicity between the downstream systems and the build automation. Putting it in one object store will make it easier to scale and to make it more reliable. | |||
== Pushlog Objects == | == Pushlog Objects == | ||
* | * | ||
== Scheduled Job Objects (valgrind, releases etc...) == | == Scheduled Job Objects (valgrind, releases etc...) == | ||
* | * There needs to be some way to see and understand what the status is of these auxiliary build/test jobs that run more periodically - valgrind, QA update tests etc. | ||
== UI Design == | == UI Design == | ||
* | * | ||
== Action Items == | == Action Items == | ||
* | * | ||