EngineeringProductivity/Projects/Treeherder: Difference between revisions
m (Edmorley moved page Auto-tools/Projects/Treeherder to EngineeringProductivity/Projects/Treeherder: A-Team has been renamed) |
(→Getting in touch: Switch to new mailing list) |
||
| Line 22: | Line 22: | ||
== Getting in touch == | == Getting in touch == | ||
* Chat on IRC: [irc://irc.mozilla.org/treeherder #treeherder] / [[IRC|learn about IRC]] / [http://logs.glob.uno/?c=treeherder channel logs] | * Chat on IRC: [irc://irc.mozilla.org/treeherder #treeherder] / [[IRC|learn about IRC]] / [http://logs.glob.uno/?c=treeherder channel logs] | ||
* Mailing list: [https://lists.mozilla.org/listinfo/ | * Mailing list: [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] (or [https://groups.google.com/forum/#!forum/mozilla.tools.treeherder via Google groups]) | ||
* Weekly meetings: [[Auto-tools/Projects/Treeherder/Meetings|Notes & dial-in details]] | * Weekly meetings: [[Auto-tools/Projects/Treeherder/Meetings|Notes & dial-in details]] | ||
Revision as of 17:00, 23 November 2015
About
Treeherder is a reporting dashboard for checkins to Mozilla projects (for example, mozilla-central or Gaia). 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.
Contributing
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
- Mozilla Treeherder instances: Staging / Production (mana page) / Deployed changes info
Source and Docs
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. View on Bugzilla
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1
Recent changes
Bugs fixed in the last 14 days. View on Bugzilla
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1