Sheriffing/TBPL/TransitionPlan: Difference between revisions
< Sheriffing | TBPL
Jump to navigation
Jump to search
(new plan) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
* Use Python + mongodb for JSON parsing and database filling instead of PHP + mysql or even node.js + mongodb | * Use Python + mongodb for JSON parsing and database filling instead of PHP + mysql or even node.js + mongodb | ||
* * Python makes gzip decrompressing easiest | ** Python makes gzip decrompressing easiest | ||
* | * Should work like this: | ||
* # Every 5 minutes | *# Every 5 minutes | ||
* # Fetch buildbot data and fill database | *# Fetch buildbot data and fill database | ||
* # Fetch Tinderbox data and add log URLs & notes to the existing records in the database | *# Fetch Tinderbox data and add log URLs & notes to the existing records in the database | ||
* # Recreate JSON files for all changed revisions | *# Recreate JSON files for all changed revisions | ||
* TBPL requests pushlog, and then for every push revision the gzipped JSON file that the python script created | * TBPL requests pushlog, and then for every push revision the gzipped JSON file that the python script created | ||
Revision as of 12:30, 24 August 2010
- Use Python + mongodb for JSON parsing and database filling instead of PHP + mysql or even node.js + mongodb
- Python makes gzip decrompressing easiest
- Should work like this:
- Every 5 minutes
- Fetch buildbot data and fill database
- Fetch Tinderbox data and add log URLs & notes to the existing records in the database
- Recreate JSON files for all changed revisions
- TBPL requests pushlog, and then for every push revision the gzipped JSON file that the python script created