Tinderbox front page improvements
- 1 Project Information
- 2 Project Details
- 3 0.3
- 4 0.2
- 5 0.1
- 6 Bug list
- 7 Project News
Tinderbox front page improvements
Tinderbox is a web app showing the results of multiple machines building Firefox, running unit tests on it, and running performance tests on it, all on three different platforms (Windows, Linux, Mac). The display is very crowded right now, and can be difficult to read. In addition, some of the interesting information (changes in performance, for example) are hard to notice. The tinderbox server software recently was updated to include JSON output, which means that webpages can now easily access the data to build their own displays. Using this data, create a new display for the Tinderbox data that helps developers monitor the status of the builds and performance data.
- Tinderbox JSON data
- An example page using the data
- Another example page using the data. (Requires a recent Firefox 3 build)
Adam Delyea - Assisted by helping me troubleshoot a local Tinderbox setup. Thanks Adam :)
We are currently looking for people who make use of Tinderbox to give their suggestions and comments on how it could be improved. Please include some specifics because the display has many areas which could be improved. Contribution ideas include what you believe would be the most important information presented, general annoyances, or things to make finding information easier on Tinderbox.
Either Leave your feedback below or contact me (Dominic) directly.
Goals - Make my existing Tinderbox code use the new json output
Now that I've got a patch that gives me a list of Tinderbox trees with basic build information I can update my code. I'll be updating the AJAX on the .html file that I created for the 0.1 to use this new information.
Goals - Implement JSON output to showbuilds.pl
In the 0.2 release the major goal will be to implement the use of JSON output into the showbuilds.pl file found in tinderbox. The reason for this is that there is currently no way of extracting per tree information in an easy way. (IE. only the tinderbox panel.htm files are available) With the release of this 0.2 JSON fix I hope to now be able to remake my tinderbox interface and submit it for use using JSON. This will make my index page in the last build less server intensive which was the main reason for its rejection.
I'm looking for people who could help me with:
- JSON - A fairly new concept to me.
- Someone to look over my code who knows perl (For efficiency and bugs)
- Always looking for interesting and good ideas to improve tinderbox layout
The 0.2 Release deals with creating a lean JSON output dynamically for all tinderbox trees available.
The patch can be found at Bug# 400708
Goals - Create index.html for tinderbox.mozilla.org
Since tinderbox.mozilla.org only redirects users to showbuilds.cgi there is no useful information presented to users immediately. The goal of the initial release will be to build a working index.html page based of Bug #366784 by Rob Helmer. The idea is to use the panels that are automatically generated by Tinderbox and put them into iFrames or the like to display a list of available trees for checkin. The idea is a layout that will look similar to the following figure.
The 0.1 Release is done. I've uploaded the files to Bug #366784 and received much feedback from the community! I'm currently awaiting review of my code by Chris Seawood and then hopefully incorporation into Tinderbox will follow!
- Bug #366784 - Request to change Tinderbox front page layout
- Bug #390341 - Support gzip encoding for Tinderbox
- Bug #381104 - Large number of builds requires horizontal scrolling
- Bug #400707 - Adding JSON output to showbuilds.pl