|
|
| (11 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| ==Goals==
| | #REDIRECT [[Auto-tools/Projects/Treeherder]] |
| | |
| * get rid of Tinderbox (bug 586539)
| |
| * be super-fast, even when going back in time
| |
| | |
| ==Necessary prereqs==
| |
| | |
| * for getting rid of Tinderbox:
| |
| ** move all the useful stuff on Tinderbox over to TBPL, specifically:
| |
| *** current sheriff (bug 540464)
| |
| *** tree state (bug 525464)
| |
| *** other notes at the top
| |
| ** put logs somewhere outside Tinderbox
| |
| *** where? (FTP is bug 530318)
| |
| ** move starring system outside Tinderbox
| |
| *** where? TBPL server?
| |
| * for being fast:
| |
| ** cache Tinderbox history on TBPL server in a database
| |
| *** for how long? a week?
| |
| *** do the same for pushlog and buildbot data?
| |
| | |
| ==Transition plan for moving away from Tinderbox==
| |
| | |
| * use data from both systems
| |
| * give TBPL a server component with a database
| |
| * put everything into TBPL's database
| |
| * correlate buildbot data with Tinderbox data if possible
| |
| ** finished Tinderbox jobs have a unique ID, buildbot jobs don't
| |
| *** create something (hash starttime + slave name?) - see bug 586539 comment 2
| |
| ** put the correlation into TBPL database
| |
| * everything using PHP and MySQL for now
| |
| | |
| ==Decisions we need to make==
| |
| | |
| * How much should happen on a server and how much on the client?
| |
| * If it doesn't happen on the client, what server should do it?
| |
| | |
| ===These things need to go on a server, no matter which one===
| |
| | |
| * Generating buildbot JSON data in the right format
| |
| ** In dbaron's experiment this is a script on dbaron's server that transforms data from build.mozilla.org
| |
| ** But we should probably generate the data in the right format on build.mozilla.org in the first place
| |
| * Starring
| |
| ** Resides in Tinderbox at the moment
| |
| * Storage and processing of logs and summaries
| |
| ** Is done by Tinderbox at the moment.
| |
| ** Plan is to upload logs to FTP (bug 530318) and to do the processing (error line linking, summary generation) on a server
| |
| * (General caching so stuff is fast)
| |