EngineeringProductivity/Projects/Treeherder: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎About: added new Intermittent Failures View page)
(update the page: removed or update outdated information)
 
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== About ==
== About ==
[https://treeherder.mozilla.org/ Treeherder] is a reporting dashboard for checkins to Mozilla projects (for example, [https://developer.mozilla.org/en-US/docs/mozilla-central 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.
[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]].
Treeherder is the successor to [[Sheriffing/TBPL|TBPL]].
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]] - also part of Treeherder.
For tracking intermittent test failures, see [[EngineeringProductivity/Projects/IntermittentFailuresView|Intermittent Failures View]].


== Contributing ==
== 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 [https://treeherder.readthedocs.io/ui/installation.html 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 these steps].
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: [http://www.joshmatthews.net/bugsahoy/?reporting=1&unowned=1 Bugs Ahoy]
* 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] / [[EngineeringProductivity/Projects/Treeherder/Bug_Triage|bug triage]]  
* 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]
* We use the [https://github.com/mozilla/autolander autolander] tool for automatically linking github pull requests to bugs.
* Mozilla Treeherder instances: [https://treeherder.allizom.org Staging] / [https://treeherder.mozilla.org Production] ([https://mana.mozilla.org/wiki/display/websites/treeherder.mozilla.org mana page]) / [http://whatsdeployed.io/?owner=mozilla&repo=treeherder&name%5B%5D=Heroku-prototype&url%5B%5D=https://treeherder-heroku.herokuapp.com/revision.txt&name%5B%5D=Stage&url%5B%5D=https://treeherder.allizom.org/revision.txt&name%5B%5D=Prod&url%5B%5D=https://treeherder.mozilla.org/revision.txt Deployed changes info]


== Source and Docs ==
== Source and Docs ==
Line 21: Line 19:
* 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: [https://github.com/mozilla/treeherder/tree/master/treeherder/client Source] / [http://treeherder.readthedocs.io/submitting_data.html#submitting-using-the-python-client docs]
** NodeJS: [https://github.com/mozilla/treeherder-node Source] / [https://github.com/mozilla/treeherder-node/blob/master/README.md README]
* Treeherder Project Debriefs
** [https://docs.google.com/document/d/1mKD4bwOTThh9gnLuM8lpKgxMDk9tZ4xnLutWho0ytDw/edit#heading=h.193nd091ylcy 2016 Q2]


== Getting in touch ==
== Getting in touch ==
* Chat on IRC: [irc://irc.mozilla.org/treeherder #treeherder] / [[IRC|learn about IRC]] / [https://mozilla.logbot.info/treeherder channel logs]
* Chat on Element: [https://chat.mozilla.org/#/room/#treeherder:mozilla.org #treeherder]
* 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: [[EngineeringProductivity/Projects/Treeherder/Meetings|Notes & dial-in details]]
 
== What we're working on ==
Assigned Treeherder bugs that have been modified in the last month.
[https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%3Atreeherder+-assignee%3Anobody%40mozilla.org+delta_ts%3E-1m View on Bugzilla]
<bugzilla stats="hide">
{
  "component": "Treeherder", "component_type": "contains",
  "resolution": "---",
  "email1": "nobody@mozilla.org", "email1_type": "not_equals", "email1_assigned_to": "1",
  "changed_after": "-1m",
  "changed_before": "Now",
  "include_fields": "id,priority,component,summary,assigned_to",
  "order": "priority,assigned_to"
}
</bugzilla>
 
== Recent changes ==
Bugs fixed in the last 14 days.
[https://bugzilla.mozilla.org/buglist.cgi?order=Bug%20Number&resolution=FIXED&chfieldto=Now&chfield=resolution&chfieldfrom=-14d&chfieldvalue=FIXED&f1=component&v1=Treeherder&o1=substring View on Bugzilla]
<bugzilla stats="hide">
{
  "component": "Treeherder", "component_type": "contains",
  "resolution": "FIXED",
  "changed_after": "-14d",
  "changed_before": "Now",
  "changed_field": "resolution",
  "changed_field_to": "FIXED",
  "include_fields": "id,component,summary,assigned_to",
  "order": "assigned_to,id"
}
</bugzilla>

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.

Source and Docs

Getting in touch

Retrieved from "https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Treeherder&oldid=1255752"