EngineeringProductivity/Projects/Treeherder: Difference between revisions
Jump to navigation
Jump to search
Full Query
(→About: added new Intermittent Failures View page) |
(Clean up out of date sections) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
For tracking performance data, see Treeherder's sister project, [[EngineeringProductivity/Projects/Perfherder|Perfherder]]. | For tracking performance data, see Treeherder's sister project, [[EngineeringProductivity/Projects/Perfherder|Perfherder]]. | ||
For tracking intermittent test failures, see [[EngineeringProductivity/Projects/IntermittentFailuresView|Intermittent Failures View]] | For tracking intermittent test failures, see [[EngineeringProductivity/Projects/IntermittentFailuresView|Intermittent Failures View]]. | ||
== Contributing == | == Contributing == | ||
To make UI changes, | To make UI-only changes, you only need to perform a very simple setup running a local webserver pointing at the production backend, described [https://treeherder.readthedocs.io/installation.html#ui-development 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 [https://treeherder.readthedocs.io/installation.html#server-and-full-stack-development these steps]. | ||
* [https://ateam-bootcamp.readthedocs.io/en/latest/ 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. | * [https://ateam-bootcamp.readthedocs.io/en/latest/ 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: [ | * Good first bugs for new developers: [https://codetribute.mozilla.org/projects/treeherder Codetribute] | ||
* Issue tracker: [https://bugzilla.mozilla.org/enter_bug.cgi?product=Tree+Management&component=Treeherder Report a bug] / [https://bugzilla.mozilla.org/query.cgi?query_format=advanced&product=Tree+Management&f1=component&o1=substring&v1=Treeherder&resolution=--- search open bugs | * Issue tracker: [https://bugzilla.mozilla.org/enter_bug.cgi?product=Tree+Management&component=Treeherder Report a bug] / [https://bugzilla.mozilla.org/query.cgi?query_format=advanced&product=Tree+Management&f1=component&o1=substring&v1=Treeherder&resolution=--- search open bugs] | ||
* Mozilla Treeherder instances: [https://treeherder.allizom.org Staging] / [https://treeherder.mozilla.org Production] / [https://whatsdeployed.io/s-dqv Deployed changes info] | |||
* Mozilla Treeherder instances: [https://treeherder.allizom.org Staging] / [https://treeherder.mozilla.org Production] | |||
== Source and Docs == | == Source and Docs == | ||
| Line 21: | Line 20: | ||
* Treeherder data submission clients: | * Treeherder data submission clients: | ||
** Pulse: [https://hg.mozilla.org/automation/mozillapulse/ Source] / [http://treeherder.readthedocs.io/submitting_data.html#submitting-using-pulse docs] | ** Pulse: [https://hg.mozilla.org/automation/mozillapulse/ Source] / [http://treeherder.readthedocs.io/submitting_data.html#submitting-using-pulse docs] | ||
** Python | ** (Python and Node submission support has been removed.) | ||
== Getting in touch == | == Getting in touch == | ||
| Line 43: | Line 39: | ||
"include_fields": "id,priority,component,summary,assigned_to", | "include_fields": "id,priority,component,summary,assigned_to", | ||
"order": "priority,assigned_to" | "order": "priority,assigned_to" | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
Latest revision as of 06:42, 11 March 2019
About
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.
Contributing
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.
- 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: Codetribute
- Issue tracker: Report a bug / search open bugs
- Mozilla Treeherder instances: Staging / Production / 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 that have been modified in the last month. View on Bugzilla
| ID | Priority | Component | Summary | Assigned to |
|---|---|---|---|---|
| 1967864 | -- | Treeherder: Frontend | ignore resolved internal issues (with associated bug) when checking for existing internal issues when internal issue filer gets used | Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) |
| 1968693 | -- | Treeherder: Frontend | do not hide resolved 'single tracking bug' in bug suggestions | Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) |
| 1970693 | -- | Treeherder: Frontend | Support ESR140 in treeherder | Bastien Orivel [:eijebong] |