BuildAPI

Project Name

BuildAPI

Project Description

The BuildAPI project consists of generating analytic reports which can be used for a multitude of purposes such as performance and usage tests or discovering rogue buildbot slave machines. Moreover, it will require querying a database for the information on the BuildBot jobs, which will then be used to generate the necessary reports.

Initial contacts: Armenzg

Project Leader(s)

Andrew Singh [1]

Jing Yang [2]

Project Contributor(s)

• Armenzg

Project Details

• Updated Objectives (October 28th 2010) from Armenzg
• We will choose one of the following to do:
  • 1) Generate graphs, charts, CSVs and CPU totals for infrastructure load blog posts like this
    • a) This is very useful and could move us forward towards having this information being published publicly for consumption
    • b) I highly encourage this one as understanding the mental model behind it is easier
  • 2)Write a tool that analyzes our statusDB and figure out slaves that have been continually been burning jobs (sometimes it takes us several days to spot them)

• Objective: To analyze and create reports from BuildBot data for multiple purposes. These reports will generated from querying buildbot databases to get the necessary information about jobs.
• It will be used for purposes such as:

• identifying critical machines that should not be processing jobs
• discovering rogue slaves
• Generating reports on performance, usage, build times, downtime, and more

• This project uses Pylons framework:

• Pylons combines the very best ideas from the worlds of Ruby, Python and Perl, providing a structured but extremely flexible Python web framework.

• We will need a snapshot of the database to test our work. For examples of the "statusdb" see:
  • http://anamariamoz.wordpress.com/
  • https://bugzilla.mozilla.org/show_bug.cgi?id=604088

• We will be generating different graphs from:
  • http://oduinn.com/blog/2010/09/09/infrastructure-load-for-august-2010/
  • Armen suggested that one student works on the first graph, and the other works on the second graph
  • We will also be working on the documentation

Project Plan

Goals for each release:

• 0.1 - Complete local installation of BuildAPI, create a script that can generate a simple graph from one of the databases based on a few criteria. Will then go into more detail in the following milestones.
• 0.2
• 0.3

Project News

• What has been done so far
  • Please see my blog at: http://andrewasdesigned.blogspot.com/2010/10/beginning-previously-we-had-conference.html
  • I have been moving forward and have installed BuildAPI locally on my machine to test it out
  • Still need time to finish reading on Pylons!

• October 22nd, 2010
  • New schedulerdb snapshot available.
• October 14, 2010:
  • Meeting of previously named "ScriptFactory" broke into three seperate projects: Mozharness, BuildAPI and Release Simple Bugs -Mustafa
  • We will follow up with Armen on details of the Release Simple Bugs project and more on BuildAPI

• Wednesday October 13, 2010:
  • The ScriptFactory group met today with Armen and Ctyler in a conference call
  • We will separate into two groups and tackle Mozharness, BuildAPI or Release Simple Bugs

Links

• Andrew Singh: http://andrewasdesigned.blogspot.com/
• Jing Yang: http://jyang42.blogspot.com/
• Armen Zambrano Gasparnian: http://armenzg.blogspot.com/
• Planet CDOT: http://zenit.senecac.on.ca/wiki/index.php/Planet_CDOT
• BuildBot Architecture: http://buildbot.net/buildbot/docs/0.8.1/images/overview.png
• Database Snapshots: http://people.mozilla.org/~catlee/schedulerdbschema.png and http://people.mozilla.org/~catlee/schema.png