cf06199a67
A json file is overkill, and it is currently in a directory intended for production-specific files, so move the blacklist inline. We should probably move the whole analyser to another file, but that can be done later. Also store the analyser output in the root of the media directory, since a subdirectory is unnecessary. The media directory is now empty, so we must use .gitkeep to ensure it is created. |
||
|---|---|---|
| bin | ||
| deployment | ||
| docs | ||
| puppet | ||
| requirements | ||
| schemas | ||
| tests | ||
| treeherder | ||
| vendor | ||
| .coveragerc | ||
| .gitignore | ||
| .landscape.yaml | ||
| .travis.yml | ||
| LICENSE.txt | ||
| README.md | ||
| Vagrantfile | ||
| manage.py | ||
| runtests.sh | ||
| setup.cfg | ||
| setup.py | ||
README.md
treeherder-service
Description
Treeherder is a reporting dashboard for Mozilla checkins. It allows users to see the results of automatic builds and their respective tests. Treeherder-service manages the etl layer for data ingestion, web services, and the data model behind Treeherder.
Treeherder is comprised of this repo for providing those back end services, and several other component repos:
A treeherder-ui repo for the front end UI.
A treeherder-client for data submission.
A treeherder-node NodeJS interface.
Instances
Treeherder exists on three instances, dev for treeherder development, stage for pre-deployment validation, and production for actual use.
Installation
The steps to install the treeherder-service are provided here.
Links
Visit our project tracking Wiki at:
https://wiki.mozilla.org/Auto-tools/Projects/Treeherder
Visit our readthedocs page for other setup and configuration at:
https://treeherder-service.readthedocs.org/en/latest/index.html
File any bugs you may encounter here.