зеркало из https://github.com/mozilla/treeherder.git
continuous-integrationdjangodjango-rest-frameworkdockerdocker-composemozillapythonreactreactjstreeherder
de7b3973c3
At some point soon we'll want to switch Heroku stage/production to their new Heroku-16 (Ubuntu 16.04) stack, so it makes sense to trial it locally first. Their Heroku-16 docker image will make switching to docker simpler too. Notable changes to the provision steps: * We're using the Bento boxes rather than the 'official' Canonical ones, at the recommendation of Vagrant: https://www.vagrantup.com/docs/boxes.html#official-boxes * openjdk-8-jre-headless is now available from the ubuntu.com repository, so doesn't require a PPA. * There isn't an official mysql-server-5.6 package (only 5.7+), so we have to start using a PPA. * Services must now be managed using systemd rather than SysV init. * The `eth0` network interface has changed name: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ * The `vendor-libmysqlclient.sh` script will still be run on Ubuntu 14.04 on Travis/Heroku for now, so has to be compatible with both. * The previous temporary cleanup steps can be removed since the vagrant destroy means a clean slate. |
||
|---|---|---|
| bin | ||
| deployment/aws | ||
| docs | ||
| lints | ||
| neutrino-custom | ||
| requirements | ||
| schemas | ||
| tests | ||
| treeherder | ||
| ui | ||
| vagrant | ||
| .coveragerc | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .slugignore | ||
| .travis.yml | ||
| LICENSE.txt | ||
| Procfile | ||
| README.md | ||
| Vagrantfile | ||
| manage.py | ||
| newrelic.ini | ||
| package.json | ||
| pylintrc | ||
| pytest.ini | ||
| requirements.txt | ||
| runtests.sh | ||
| runtime.txt | ||
| setup.cfg | ||
| setup.py | ||
| 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.