generic-library/webrtc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Completed implementation of oauth in coverage scripts.

Browse Source 
The access token is now transferred between the request and track scripts.

Almost completed the implementation, using oauth2.

Initial, incomplete implementation of the permission-request script.

The coverage tracking is broken temporarily, but it can now make OAuth requests.

BUG=
TEST=

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

git-svn-id: http://webrtc.googlecode.com/svn/trunk@1530 4adac7df-926f-26a2-2b94-8c16560cd09d
This commit is contained in:
phoglund@webrtc.org
2012-01-24 14:44:51 +00:00
parent 28a5cb29ab
commit 96c39d1f73
7 changed files with 262 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
tools/coverage/README
View File

@@ -7,10 +7,18 @@ 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 communicates with the dashboard using plain GET
requests (that, and POST, are basically the only way to get data into a
appengine application such as the dashboard). The dashboard is intented to
run on the Google appengine.
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: