commit | 97ac1d26995b60f5878a70d5bd1fd5b268879aa1 | [log] [tgz] |
---|---|---|
author | Chris McDonald <cjmcdonald@chromium.org> | Fri Jun 28 20:45:36 2019 |
committer | Chris McDonald <cjmcdonald@chromium.org> | Fri Jun 28 20:45:36 2019 |
tree | 1e1dae354fa276a1260a595cc431ddba78fcdb85 | |
parent | 2b776e5bd575c2373bcecc990057b6bbeaeba7b5 [diff] |
cl_exonerator: Add OWNERS file This CL is populating OWNERS file based on the candidates in the Chrome OS OWNERS status sheet. BUG=b:132095048 TEST=None Change-Id: I09cd9dffde5e013a2f353b8e86432ed3968a71a2
https://chromium.googlesource.com/chromiumos/infra/cl_exonerator
This app finds CLs which were incorrectly blamed for a CQ failure, and re-marks them as CQ-ready. It does this by polling cidb‘s buildMessageTable for finalize messages, then finds CLs which were blamed in the build’s annotatations and marks them as CQ+1 in Gerrit (if they haven't already been).
Create a “creds” folder, then:
For local development, run “cros cidbcreds --folder=creds/cidb” to fetch the readonly credentials.
For deploying to production, see go/cros-cidb-admin and get the prod_cidb_gen2_annotator credentials.
Local deployment is done by creating a virtualenv with pipenv:
# pipsi is a nice python utility for installing other python scripts in their # own virtualenvs, so you don't get version conflicts between the various # scripts installed on your system. sudo `which pip` install pipsi pipsi install pipenv pipenv install --dev pipenv shell
Tests are run with pytest:
pipenv run pytest exonerator
Start a development server with bin/local_server
and run curl -u admin http://localhost:8080/cls?type=pending
to see a list of pending CLs.
CL-Exonerator is deployed to the google.com:chromiumos-cl-exonerator project. Before deploying, make sure you have activated it as your default project with gcloud:
gcloud config set project chromiumos-cl-exonerator
Then deploy with the ./deploy_app script:
pipenv shell ./deploy_app
Run ./deploy_app --debug=True after copying or symlinking debug_cidbi_gen2_bot creds into ./creds/cidb.dbg (see the [Credentials][#Credentials] section)
Run “./deploy_app” after copying or symlinking prod_cidb_gen2_bot creds into “./creds/cidb”.