2e4e3a4dda
* Add management task for fetching github commits based on repository fixes and 2 tables for storing that data * Add changelog web api * Add tests * Refactor Github utilities into one file and move http utilities from common.py to new file |
||
|---|---|---|
| .dependabot | ||
| bin | ||
| deployment/aws | ||
| docker | ||
| docs | ||
| lints | ||
| misc | ||
| requirements | ||
| schemas | ||
| tests | ||
| treeherder | ||
| ui | ||
| .codecov.yml | ||
| .dockerignore | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .neutrinorc.js | ||
| .pre-commit-config.yaml | ||
| .prettierignore | ||
| .prettierrc.js | ||
| .readthedocs.yml | ||
| .renovaterc | ||
| .slugignore | ||
| .travis.yml | ||
| .yarnrc | ||
| CODE_OF_CONDUCT.md | ||
| LICENSE.txt | ||
| Procfile | ||
| README.md | ||
| app.json | ||
| docker-compose.yml | ||
| initialize_data.sh | ||
| jest.config.js | ||
| manage.py | ||
| mkdocs.yml | ||
| newrelic.ini | ||
| package.json | ||
| pylintrc | ||
| requirements.txt | ||
| runtests.sh | ||
| runtime.txt | ||
| setup.cfg | ||
| webpack.config.js | ||
| yarn.lock | ||
README.md
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, stage 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 at: https://wiki.mozilla.org/EngineeringProductivity/Projects/Treeherder
Visit our readthedocs page for other setup and configuration at: https://treeherder.readthedocs.io
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 adressing 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.