Treeherder
| Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
|---|---|---|---|---|---|---|---|---|---|---|
| Debugger | 4,605 |  | 11 | 3 | 9 months ago | 13 | December 15, 2016 | |||
| The faster and smarter Debugger for Firefox DevTools 🔥🦊🛠 | ||||||||||
| React Typescript Web Extension Starter | 833 | 2 months ago | 3 | December 11, 2020 | 7 | mit | JavaScript | |||
| :desktop_computer: Web Extension starter kit built with React, TypeScript, TailwindCSS, Storybook, Jest, EsLint, Prettier, and Webpack. Supports Google Chrome + Mozilla Firefox + Brave Browser + Microsoft Edge + Opera :fire: | ||||||||||
| Addons Frontend | 528 | 2 days ago | 31 | March 22, 2022 | 228 | mpl-2.0 | JavaScript | |||
| Front-end to complement mozilla/addons-server | ||||||||||
| Treeherder | 240 | | 63 | 2 | 7 hours ago | 15 | February 20, 2019 | 22 | other | JavaScript |
| A system for managing CI data for Mozilla projects | ||||||||||
| Span Tree | 207 | 3 months ago | 7 | mit | CSS | |||||
| 🌳 Tree for GitLab | ||||||||||
| React File Base64 | 93 |  | 63 | 9 | 4 years ago | 4 | August 05, 2017 | 14 | mit | JavaScript |
| React Component for Converting File to base64 | ||||||||||
| Firefox Performance Dashboards | 62 | a month ago | 51 | mpl-2.0 | JavaScript | |||||
| Firefox's performance dashboard | ||||||||||
| React Native L20n | 29 | 7 years ago | 8 | October 05, 2016 | mit | JavaScript | ||||
| Mozilla's L20n localization framework for React Native | ||||||||||
| Firefox Health Dashboard | 26 | 2 years ago | mpl-2.0 | JavaScript | ||||||
| Front End Learning | 26 | 2 years ago | ||||||||
| A list of resources for both learning & keeping up with web development. | ||||||||||
Treeherder
Description
Treeherder is a reporting dashboard for Mozilla checkins. It allows users to see the results of automatic builds and their respective tests. The Treeherder service manages the etl layer for data ingestion, web services, and the data model behind Treeherder.
Instances
Treeherder exists on two instances: staging for pre-deployment validation, and production for actual use.
Installation
The steps to run Treeherder are provided here.
The steps to run only the UI are provided here.
Links
Visit our project tracking Wiki here.
For other setup and configuration, visit our readthedocs page here.
File any bugs you may encounter here.
Contributing
Everyone is welcome to contribute!
If a bug is not assigned to someone, you can request the bug be assigned to you. You should ask the component owner with your request ("Request information" in Bugzilla and mention in Github).
If you do not receive a response within 2-3 days, you can follow up in the #treeherder matrix channel.
After addressing the issue, make sure every test passes before sending a pull request.
We also recommend setting an upstream remote that points to the Mozilla's Github repo, in addition to origin that points to your fork. You should then frequently use git rebase upstream rather than merging from your fork to keep your branch current. There are less conflicts this way and the git history is cleaner.
Sending a Pull Request
We receive contributions from both Bugzilla and Github. We have some specifications to keep track of them:
-
If your bug comes from Bugzilla
After addressing the issue, please send a pull request to this repository, with the Bugzilla's number ID in the title, so that our bot attaches your patch to the corresponding Bugzilla bug.
"Bug xxxxxx - [title of the bug or brief explanation]"For example: "Bug 123456 - Fix scrolling behavior in Perfherder"
-
If your bug comes from Github
In the description of the pull request, please mention the issue number. That can be done by typing #[issue's number].
For example: "This pull request fixes #5135".
Github automatically links both issue and pull request to one another.
