webrtc/tools/quality_tracking
kjellander@webrtc.org 1bc6d3238c Only status from interesting bots are reported to the Dashboard
TBR=phoglund
BUG=none
TEST=Tested with local modifications on the live installation.

Review URL: https://webrtc-codereview.appspot.com/675005

git-svn-id: http://webrtc.googlecode.com/svn/trunk@2496 4adac7df-926f-26a2-2b94-8c16560cd09d
2012-07-09 09:43:30 +00:00
..
dashboard Rewired the oath2 symlink and updated tgrid_parser to the new Build Bot version's tgrid syntax. 2012-04-17 08:49:10 +00:00
constants.py Fixed bugs in the coverage tracker. 2012-03-01 15:50:30 +00:00
dashboard_connection.py Made the necessary adaptations for the dashboard launch and fixed some bugs (already live). 2012-02-27 15:42:25 +00:00
oauth2 Rewired the oath2 symlink and updated tgrid_parser to the new Build Bot version's tgrid syntax. 2012-04-17 08:49:10 +00:00
OWNERS Refactored the dashboard in order to add new functionality and added some new functionality. 2012-02-01 10:59:23 +00:00
README Refactored the dashboard in order to add new functionality and added some new functionality. 2012-02-01 10:59:23 +00:00
request_oauth_permission.py Made the necessary adaptations for the dashboard launch and fixed some bugs (already live). 2012-02-27 15:42:25 +00:00
tgrid_parser_test.py Fixed some unexpected syntax for chrome bots. 2012-05-16 09:05:57 +00:00
tgrid_parser.py Fixed some unexpected syntax for chrome bots. 2012-05-16 09:05:57 +00:00
track_build_status_test.py Only status from interesting bots are reported to the Dashboard 2012-07-09 09:43:30 +00:00
track_build_status.py Only status from interesting bots are reported to the Dashboard 2012-07-09 09:43:30 +00:00
track_coverage.py Implemented branch coverage and integration bot coverage on the dashboard. 2012-03-12 09:12:32 +00:00

This file describes the coverage tracking script and the coverage dashboard.

ABSTRACT:
The intention of this small tracking system is to track code coverage data
over time. Since code coverage is continuously recomputed on the build bots,
the track_coverage.py script is intended to run on the build bot as a cron job
and extract the data from there. The dashboard doesn't care how often this
script runs, but running each hour should be more than enough.

The track_coverage.py script uses OAuth to authenticate itself. In order to do
this, it needs two files: consumer.secret and access.token. The consumer secret
is known within the organization and is stored in a plain file on the bot 
running the scripts (we don't want to check in this secret in the code in the
public repository). The consumer secret is a plain file with a single line
containing the secret string.

The access.token file is generated by request_oauth_permission.py. It does this
by going through the three-legged OAuth authorization process. An administrator
of the dashboard must approve the request from the script. Once that is done,
access.token will be written and track_coverage.py will be able to report
results.

HOW TO RUN LOCALLY:
Follow the following instructions:
http://code.google.com/appengine/docs/python/gettingstartedpython27/devenvironment.html
The dashboard can be started on 127.0.0.1:8080 using the dev_appserver.py script 
as described in the above URL (and in the following 'hello world' page).

HOW TO DEPLOY:
Follow the following instructions:
http://code.google.com/appengine/docs/python/gettingstartedpython27/uploading.html