EngineeringProductivity/Projects/Treeherder: Difference between revisions
(→Source and Docs: client changes) |
(→Bug Tables: Update bug queries now that the perfherder component name has changed) |
||
| Line 37: | Line 37: | ||
<bugzilla> | <bugzilla> | ||
{ | { | ||
"quicksearch": ":treeherder | "quicksearch": ":treeherder priority:P1,P2 assignee:nobody@mozilla.org", | ||
"include_fields": "id,priority,component,summary", | "include_fields": "id,priority,component,summary", | ||
"order": "priority,component" | "order": "priority,component" | ||
| Line 43: | Line 43: | ||
</bugzilla> | </bugzilla> | ||
=== [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%3Atreeherder+priority%3A--+assignee%3Anobody%40mozilla.org Needing Triage] === | === [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%3Atreeherder+priority%3A--+assignee%3Anobody%40mozilla.org Needing Triage] === | ||
All bugs that do not have a priority set and are unassigned | All bugs that do not have a priority set and are unassigned. | ||
<bugzilla> | <bugzilla> | ||
{ | { | ||
" | "component": "Treeherder", "component_type": "contains", | ||
"resolution": "---", | |||
"priority": "--", | |||
"assignee": "nobody@mozilla.org", | |||
"include_fields": "id,component,summary", | "include_fields": "id,component,summary", | ||
"order": "component" | "order": "component" | ||
Revision as of 10:54, 2 May 2015
Overview
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 API's that can be used by other projects interested in this information.
Treeherder is the successor to TBPL.
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 both the treeherder-ui and treeherder-service Github repos as a pair, following 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
- Bugzilla: File a bug / All open bugs / Recently fixed / Bug tables
- Chat on IRC: #treeherder / Channel logs (to learn about IRC see IRC)
- Mailing list: dev.tree-management (or via Google groups)
- Meetings: Notes & dial-in details
- Mozilla Treeherder instances: Dev / Staging / Production (mana page)
Source and Docs
Bug Tables
Assigned
A summary of Treeherder bugs that are being worked on at the moment.
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1
Unassigned P1-2
Ideally these are the bugs that should be worked on next, once the currently assigned bugs are fixed.
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1
Needing Triage
All bugs that do not have a priority set and are unassigned.
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1
All open bugs
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1
Recently fixed
Bugs changed to "Resolved FIXED" in the last 14 days.
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1