EngineeringProductivity/Projects/Treeherder: Difference between revisions
m (→All Others: Case change) |
(update the page: removed or update outdated information) |
||
| (116 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
== | == About == | ||
[https://treeherder.mozilla.org/ Treeherder] is | [https://treeherder.mozilla.org/ Treeherder] is a reporting dashboard for checkins to Mozilla projects (for example, [https://github.com/mozilla-firefox/firefox mozilla-firefox/firefox's "main" also known as "mozilla-central" branch]). 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 [[Sheriffing/TBPL|TBPL]]. | |||
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]]. | |||
== | == 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 [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. | |||
* 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://prototype.treeherder.nonprod.cloudops.mozgcp.net/ Prototype] / [https://treeherder.allizom.org Staging] / [https://treeherder.mozilla.org Production] / [https://whatsdeployed.io/s-dqv Deployed changes info] | |||
=== [https:// | == Source and Docs == | ||
* UI & backend: [https://github.com/mozilla/treeherder Source] / [https://treeherder.readthedocs.io Docs] | |||
* Treeherder data submission clients: | |||
** Pulse: [https://hg.mozilla.org/automation/mozillapulse/ Source] / [http://treeherder.readthedocs.io/submitting_data.html#submitting-using-pulse docs] | |||
== | == Getting in touch == | ||
* [https:// | * Chat on Element: [https://chat.mozilla.org/#/room/#treeherder:mozilla.org #treeherder] | ||
Latest revision as of 10:21, 24 November 2025
About
Treeherder is a reporting dashboard for checkins to Mozilla projects (for example, mozilla-firefox/firefox's "main" also known as "mozilla-central" branch). 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.
- Issue tracker: Report a bug / search open bugs
- Mozilla Treeherder instances: Prototype / Staging / Production / Deployed changes info
Source and Docs
Getting in touch
- Chat on Element: #treeherder