EngineeringProductivity/Projects/Treeherder/Meetings/2013-01-30: Difference between revisions
< EngineeringProductivity | Projects | Treeherder | Meetings
Jump to navigation
Jump to search
(Created page with "= Design Notes = == Build Objects == * == Test Objects == * == Pushlog Objects == * == Scheduled Job Objects (valgrind, releases etc...) == * == UI Design == * == Action Items == *") |
m (Edmorley moved page Auto-tools/Projects/Treeherder/Meetings/2013-01-30 to EngineeringProductivity/Projects/Treeherder/Meetings/2013-01-30: A-Team has been renamed) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Design Notes = | = Design Notes = | ||
Meeting [https://etherpad.mozilla.org/0UNompHcLU etherpad] | |||
For each design category, we need the following: | |||
* Object and index structure | |||
* How/where to get the data? | |||
* How to present the data? | |||
* How do we integrate the object with other object stores? | |||
* NOTE: Meeting discussion is getting moved to pivotal tracker. edmorley has an interesting idea regarding modeling job requests... More on this soon. | |||
== Build Objects == | == Build Objects == | ||
* | * Think Bob the Builder but with objects instead of trains | ||
== Test Objects == | == Test Objects == | ||
* | * More objects less parsing | ||
== Pushlog Objects == | == Pushlog Objects == | ||
* | * Everyone marches in line | ||
== Scheduled Job Objects (valgrind, releases etc...) == | == Scheduled Job Objects (valgrind, releases etc...) == | ||
* | * Ahhh it's never simple is it... | ||
== Machine State Objects == | |||
* List of machines and their current state for each build system | |||
== Putting it All Together == | |||
* Well balanced simple hi energy diet with no spaghetti | |||
== UI Design == | == UI Design == | ||
* | * We will actually get to this some day... no really... | ||
== Action Items == | == Action Items == | ||
* | * Action Jackson is on the way! | ||
Latest revision as of 16:48, 23 November 2015
Design Notes
Meeting etherpad
For each design category, we need the following:
- Object and index structure
- How/where to get the data?
- How to present the data?
- How do we integrate the object with other object stores?
- NOTE: Meeting discussion is getting moved to pivotal tracker. edmorley has an interesting idea regarding modeling job requests... More on this soon.
Build Objects
- Think Bob the Builder but with objects instead of trains
Test Objects
- More objects less parsing
Pushlog Objects
- Everyone marches in line
Scheduled Job Objects (valgrind, releases etc...)
- Ahhh it's never simple is it...
Machine State Objects
- List of machines and their current state for each build system
Putting it All Together
- Well balanced simple hi energy diet with no spaghetti
UI Design
- We will actually get to this some day... no really...
Action Items
- Action Jackson is on the way!