Sheriffing/TBPL/FuturePlans: Difference between revisions

arpads ideas
(next actions)
(arpads ideas)
Line 74: Line 74:


* Pushlog data still only cached by Pushlog itself
* Pushlog data still only cached by Pushlog itself
** Load will be reduced significantly when the new Pushlog JSON is in place (bug XXX)
** Load will be reduced significantly when the new Pushlog JSON is in place (bug 584836, waiting to be deployed: bug 585882)
* Tinderbox data cached in TBPL database
* Tinderbox data cached in TBPL database
* Buildbot data cached in TBPL database
* Buildbot data cached in TBPL database
Line 97: Line 97:
# Create a script that reads from the database and sends this kind of data
# Create a script that reads from the database and sends this kind of data
# ... more to come
# ... more to come
==Arpad’s ideas==
* bitrotted server and client implementation in bug 553549
** based on php, mysql; parses pushlog html and tinderbox json
** revived the client part in bug 576489, bitrotted a bit again :(, would like to wait for pl json and tb json2 before continuing work
* how fast is the new pushlog json? does it beat a custom database?
** the json includes the list of changed files which is irrelevant to tbpl
* how to properly handle builds that pull from multiple repos (preliminaty ui in bug 587761)
** builds.m.o json has confusing attribute names for multi-repo builds
** want to display multiple pushlogs side-by-side, or easy switching without the need to reload the data
** what happens for "no pushes between X and Y" cases (see next point)
* "how many pushlog entries I can see" vs. time-based queries; former needs dynamic database access as opposed to pregenerated json files
** history-as-you-scroll
* playing around with node.js and MongoDB, however mongodb driver for node is slow.
** could do log preprocessing and bug suggestion in node when the tb json is loaded and save result to database
Confirmed users
9

edits