EngineeringProductivity/Projects/Treeherder: Difference between revisions
Mitchhentges (talk | contribs) (Update Python docs reference, add Pulse to list of Treeherder data submission clients) |
m (→Getting in touch: Update logbot URL) |
||
| Line 25: | Line 25: | ||
== Getting in touch == | == Getting in touch == | ||
* Chat on IRC: [irc://irc.mozilla.org/treeherder #treeherder] / [[IRC|learn about IRC]] / [ | * 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: [[EngineeringProductivity/Projects/Treeherder/Meetings|Notes & dial-in details]] | * Weekly meetings: [[EngineeringProductivity/Projects/Treeherder/Meetings|Notes & dial-in details]] | ||
Revision as of 13:50, 8 February 2018
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.
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 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: Bugs Ahoy
- Issue tracker: Report a bug / search open bugs / bug triage
- We use the autolander tool for automatically linking github pull requests to bugs.
- Mozilla Treeherder instances: Staging / Production (mana page) / 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] |
Recent changes
Bugs fixed in the last 14 days. View on Bugzilla
| ID | Component | Summary | Assigned to |
|---|---|---|---|
| 1964783 | Treeherder | Add support for converting a lando commit ID parameter into a treeherder revision | Greg Mierzwinski [:sparky] |
| 1970133 | Treeherder: Frontend | add linux 24.04 pretty names to treeherder | Julien Cristau [:jcristau] |
| 1923919 | Treeherder: Frontend | only reopen bugs once we hit 3 instances in a given week | |
| 1923922 | Treeherder: Frontend | only comment on bugs once we hit 3 instances in a given week |