EngineeringProductivity/Projects/Treeherder: Difference between revisions

m (→‎Getting in touch: Update logs link)
(Clean up out of date sections)
 
(8 intermediate revisions by 5 users not shown)
Line 5: Line 5:


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]].


== 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.org/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.org/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.org/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]
* 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] / [[EngineeringProductivity/Projects/Treeherder/Bug_Triage|bug triage]]  
* 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]
* 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://whatsdeployed.io/s-dqv Deployed changes info]
* 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 ==
* UI & backend: [https://github.com/mozilla/treeherder Source] / [https://treeherder.readthedocs.org Docs]
* UI & backend: [https://github.com/mozilla/treeherder Source] / [https://treeherder.readthedocs.io Docs]
* Treeherder data submission clients:
* Treeherder data submission clients:
** Python: [https://github.com/mozilla/treeherder/tree/master/treeherder/client Source] / [http://treeherder.readthedocs.org/en/latest/submitting_data.html docs]
** Pulse: [https://hg.mozilla.org/automation/mozillapulse/ Source] / [http://treeherder.readthedocs.io/submitting_data.html#submitting-using-pulse docs]
** NodeJS: [https://github.com/mozilla/treeherder-node Source] / [https://github.com/mozilla/treeherder-node/blob/master/README.md README]
** (Python and Node submission support has been removed.)


== Getting in touch ==
== Getting in touch ==
* Chat on IRC: [irc://irc.mozilla.org/treeherder #treeherder] / [[IRC|learn about IRC]] / [http://logs.glob.uno/?c=mozilla%23treeherder channel logs]
* Chat on IRC: [irc://irc.mozilla.org/treeherder #treeherder] / [[IRC|learn about IRC]] / [https://mozilla.logbot.info/treeherder channel logs]
* Mailing list: [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] (or [https://groups.google.com/forum/#!forum/mozilla.tools.treeherder via Google groups])
* 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: [[EngineeringProductivity/Projects/Treeherder/Meetings|Notes & dial-in details]]


== What we're working on ==
== What we're working on ==
Line 38: 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>
== 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>
</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.

Source and Docs

  • UI & backend: Source / Docs
  • Treeherder data submission clients:
    • Pulse: Source / docs
    • (Python and Node submission support has been removed.)

Getting in touch

What we're working on

Assigned Treeherder bugs that have been modified in the last month. View on Bugzilla

Full Query
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)