Skip to content
A tool to generate documentation of the differences between Bugzilla schema versions
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Bugzilla Schema Doc Generation

1. Introduction

This repository contains the code and documents used to generate the online Bugzilla schema documentation, produced as a side-benefit of the Perforce Defect Tracking Integration project.

Please note:

  • this has not been substantially updated since 2009, and the last schema contained in the data is for Bugzilla 3.3.4. We don't have an ongoing business case for maintaining it.
  • it was written and has been maintained in a very ad-hoc fashion, and the job which it aims to achieve is intrinsically complex. We are not proud of this code.

Please fork it and bring it up to date!

2. Index

File Description A Python module to interrogate MySQL to obtain a live database schema, and to write a "pickled" version of that schema into a file in the "pickles" directory.
pickles A directory containing pickled versions of every Bugzilla database schema, generated by Each pickle is named after the first version of Bugzilla which had that schema. A Python module to read a pickled schema from the "pickles" directory, annotate it with data from, and convert it to a canonical Python dictionary form. A Python module defining all the comments and running text which are ever used in the generated documentation (excluding automatically-generated text such as field names, types, attributes, and notes on schema changes). Also lists the schemas available in "pickles", and provides the mapping from Bugzilla version to schema version name. The main Python documentation generation module. Uses the unpickled schemas fetched by, compares them to identify schema changes and colour the resulting charts, processes the text to include comments appropriate to the range of schemas requested, and automated comments reflecting the schema version ranges specific to particular pieces of commentary, and produces the resulting HTML document. The front-end CGI script which presents a form, validates input through the form, and drives make_schema_doc to produce the schema documentation.
index.cgi A tiny Python script which uses to do all of the CGI work. The two files are separated so that the source of can be published directly through the same web interface as the generated schemas.

3. Requirements

For hosting:

  • Python
  • a web server that can run Python CGI.

For updating:

  • The above, and also:
  • The ability to create Bugzilla installations for different versions of Bugzilla, using MySQL.
  • MySQLdb.
  • Understanding of Perl, and of Bugzilla internals.
  • Patience.

For guidance on updating the tool to handle newer Bugzilla releases, see updating.rst.

You can’t perform that action at this time.