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 changes, in many cases you only need to perform a very simple setup running a local webserver pointing at the production instance, 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.
- A-Team Bootcamp: Best practices for working on A-Team projects (of which Treeherder is one), including valuable information on using Git and Bugzilla. If you're new to Mozilla or the A-Team, please read this guide thoroughly before proceeding.
- Good first bugs for new developers: Bugs Ahoy
- Issue tracker: Report a bug / search open bugs / bug triage
- We use the autolander tool for automatically linking github pull requests to bugs.
- Mozilla Treeherder instances: Staging / Production (mana page) / Deployed changes info
Source and Docs
- UI & backend: Source / Docs
- Treeherder data submission clients:
- Treeherder Project Debriefs
Getting in touch
- Chat on IRC: #treeherder / learn about IRC / channel logs
- Mailing list: tools-treeherder (or via Google groups)
- Weekly meetings: Notes & dial-in details
What we're working on
Assigned Treeherder bugs that have been modified in the last month. View on Bugzilla
Bugs fixed in the last 14 days. View on Bugzilla