A system for managing CI data for Mozilla projects
Alternatives To Treeherder
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Debugger4,6051139 months ago13December 15, 2016
The faster and smarter Debugger for Firefox DevTools 🔥🦊🛠
React Typescript Web Extension Starter833
2 months ago3December 11, 20207mitJavaScript
: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 Frontend528
2 days ago31March 22, 2022228mpl-2.0JavaScript
Front-end to complement mozilla/addons-server
Treeherder2406327 hours ago15February 20, 201922otherJavaScript
A system for managing CI data for Mozilla projects
Span Tree207
3 months ago7mitCSS
🌳 Tree for GitLab
React File Base64936394 years ago4August 05, 201714mitJavaScript
React Component for Converting File to base64
Firefox Performance Dashboards62
a month ago51mpl-2.0JavaScript
Firefox's performance dashboard
React Native L20n29
7 years ago8October 05, 2016mitJavaScript
Mozilla's L20n localization framework for React Native
Firefox Health Dashboard26
2 years agompl-2.0JavaScript
Front End Learning26
2 years ago
A list of resources for both learning & keeping up with web development.
Alternatives To Treeherder
Select To Compare

Alternative Project Comparisons


What's Deployed Build Status Node dependencies Status Documentation Status Code style: black


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.


Treeherder exists on two instances: staging for pre-deployment validation, and production for actual use.


The steps to run Treeherder are provided here.

The steps to run only the UI are provided here.


Visit our project tracking Wiki here.

For other setup and configuration, visit our readthedocs page here.

File any bugs you may encounter here.


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:

  1. 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"

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

Popular Mozilla Projects
Popular Reactjs Projects
Popular Companies Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
Continuous Integration
Docker Compose
Pull Requests
Django Rest Framework