Google Git
Sign in
chromium / chromiumos / infra / cl_exonerator / firmware-poppy-10431.B
commit29ec8f7c704596b7293e9bd140cacfa09fdd95b1[log] [tgz]
authorPaul Hobbs <phobbs@google.com>Thu Nov 30 08:28:18 2017
committerPaul Hobbs <phobbs@google.com>Fri Dec 01 19:24:34 2017
tree605f1664648dcd76deb7f010cb5d22bfd842a944
parentd028360ec476357b7c584a5ee7874663342fb061 [diff]
local_server: Add --port option.

Also, only use 1 worker process. This reduces the log noise when you interrupt
the server, as each child process dumps a stacktrace.

BUG=chromium:756762
TEST=Used it.

Change-Id: If28c0478a69b3b54395e84e734ca26b9e64e63fc
1 file changed
tree: 605f1664648dcd76deb7f010cb5d22bfd842a944
  1. bin/
  2. exonerator/
  3. chromite ⇨ ../../chromite
  4. pylintrc ⇨ ../../chromite/pylintrc
  5. .gitignore
  6. app.yaml
  7. config.py
  8. cron.yaml
  9. debug_routes.py
  10. debug_routes_test.py
  11. deploy_app.py
  12. gunicorn.conf.py
  13. main.py
  14. Pipfile
  15. Pipfile.lock
  16. PRESUBMIT.cfg
  17. pytest.ini
  18. README.md
README.md

CL Exonerator

https://chromium.googlesource.com/chromiumos/infra/cl_exonerator

Purpose:

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).

Credentials

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_bot credentials.

Development

Local deployment is done by creating a virtualenv from requirements.txt:

virtualenv --python=`which python2` en
source env/bin/activate
pip install -r dev_requirements.txt

Then, install the Google App Engine SDK and either symlink it or copy it into the virtualenv. Assuming the google appengine SDK is installed at $GAE, run

cp -r $GAE/* env/lib/python2.7/site-packages

Tests are run with pytest. Some tests require a chroot; enter with “cros chroot.” The virtualenv will need to be created inside the chroot, or with “virtualenv --relocateable” for this to work.

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.

Deployment

  • Debug environment:

Run ./deploy_app --debug=True after copying or symlinking debug_cidbi_gen2_bot creds into ./creds/cidb.dbg (see the [Credentials][#Credentials] section)

  • Production:

Run “./deploy_app” after copying or symlinking prod_cidb_gen2_bot creds into “./creds/cidb”.