From MozillaWiki
Jump to: navigation, search


Treeherder is a reporting dashboard for checkins to Mozilla projects (for example, mozilla-central). It allows users to see the results of automatic builds and their respective tests. Treeherder also provides a rich set of APIs that can be used by other projects interested in this information.

Treeherder is the successor to TBPL.

For tracking performance data, see Treeherder's sister project, Perfherder.

For tracking intermittent test failures, see Intermittent Failures View.


To make UI-only changes, you only need to perform a very simple setup running a local webserver pointing at the production backend, described here. If you wish to hack on the backend, or the UI and backend together, you will instead need to set up a Vagrant environment, using these steps.

Source and Docs

  • UI & backend: Source / Docs
  • Treeherder data submission clients:
    • Pulse: Source / docs
    • (Python and Node submission support has been removed.)

Getting in touch

What we're working on

Assigned Treeherder bugs that have been modified in the last month. View on Bugzilla

Full Query
ID Priority Component Summary Assigned to
1598422 P3 Treeherder: Frontend Add pernosco treeherder integration Sarah Clements [:sclements]
1731631 -- Treeherder: Log Parsing & Classification classify failures with open bugs instead of duplicate bugs whose summaries match the failure lines Sebastian Hengst [:aryx] (needinfo on intermittent or backout)
1730918 -- Treeherder: Log Parsing & Classification support different default security bugs per Bugzilla product in bug filer Sebastian Hengst [:aryx] (needinfo on intermittent or backout)
1730922 -- Treeherder: Log Parsing & Classification explain why bug created from Treeherder is set as security bug Sebastian Hengst [:aryx] (needinfo on intermittent or backout)
1674462 -- Treeherder: Log Parsing & Classification don't set a priority and severity for bugs filed for crashes in automation Sebastian Hengst [:aryx] (needinfo on intermittent or backout)