Mozilla BuildBot Trending
- 1 Project Name
- 2 Project Description
- 3 Project Leader(s)
- 4 Project Contributor(s)
- 5 Project Details
- 6 Project Wiki Pages
- 7 Project Plan
- 7.1 Step 1
- 7.2 Step 2
- 7.2.1 0.142 - Setup Local Buildbot
- 7.2.2 0.285 - Make a (successful) change to BuildBot/Twisted
- 7.2.3 0.428 - Patch BuildBot to add timestamps
- 7.2.4 0.571 - Design Database Schema
- 7.2.5 0.714 - Log to Database Connector
- 7.2.6 0.857 - Design UI for trending information
- 7.2.7 1.00 - Implement UI for trending informaion
- 7.3 Step 3
Mozilla BuildBot Trending
This project aims to provide more information from the build system.
John Ford is leading this project
Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki
NOTE: only Project Leader(s) should add names here. You can’t add your own name to the Contributor list.
Currently, it is very difficult to figure out how much time is being spent in each part of the build system. Very high level tasks are timed, like checkout, build, test, but individual steps aren't being timed.
Project Wiki Pages
This project will be broken into many distinct parts. Step 2 will be completed for DPS911. As I don't know what this project holds, I have more solid details of the first few releases. As I work through the first few parts of the system, I will be able to add detail to this page.
I need to come up with a name :)
Break It Down
I guess this is what I am doing here
0.142 - Setup Local Buildbot
This step will be to set up buildbot at CDOT. This system will serve a dual purpose of having a local Buildbot system for use in CDOT as well as allowing me to test changes to buildbot. If having a local stable buildbot is found to be useful, an additional one can be set up. Initially, this local Buildbot will have a single CentOS Slave, though, as time goes on more slaves will be added.
I plan to put the buildbot master on Australia and use either KVM based Virtual Machines or bare metal machines.
0.285 - Make a (successful) change to BuildBot/Twisted
This step involves making a change to buildbot which doesn't horribly break the system. By this release I would like to have at least one Windows and one OS X machine as slaves to ensure that nothing is broken for the individual build systems. This step will serve as a learning tool for my next step and make me familiar with the BuildBot codebase
0.428 - Patch BuildBot to add timestamps
As I understand it, buildbot uses Twisted's twisted.python.log.msg() method to log everything. I will modify this function to interface with some sort of information gathering system and create a configuration option in buildbot to use this option. The patches which will accomplish this will be submitted upstream.
0.571 - Design Database Schema
The log parser will need somewhere to put the information it finds in the logs. Currently, the best place to put this is a database. I will design the schema required for storing data. My goal is to have this be able to store information for different branches, each with their own history. This release will be in the form of a diagram illustrating the design.
0.714 - Log to Database Connector
This release will involve creating a way of getting data from the buildbot into the database. Currently, a parsing program is planned which will run on the logs of buildbot which have had timestamps added. Other options include having buildbot directly interface with the database and wrapping the individual build tools.
0.857 - Design UI for trending information
This step involves designing the UI for the trending information. It will include relevant information which is known to be representable from the data collected earlier.
1.00 - Implement UI for trending informaion
I will implement this UI. I plan to make a web front end to the system.
This step will not be broken down into distinct chunks yet as I would like to get familiar with buildbot and the overall build-test cycle before I start planning this part of the system. This step involves keeping track of historical information found during builds and their error logs. This portion of the system will help isolate recurring issues by making note of which machines are falling which test runs and why. A potential idea is to integrate some sort of 'learning' mechanism to help find patterns in build output which are known to be caused by a specific problem.