commit | 3dc05370c433887ceb73a8b31d45061d8678edd4 | [log] [tgz] |
---|---|---|
author | Paul Hobbs <phobbs@google.com> | Fri Mar 02 00:26:47 2018 |
committer | chrome-bot <chrome-bot@chromium.org> | Sat Mar 10 09:27:45 2018 |
tree | cba27e1d19f26f555c04fed8c8aedcbbf441c181 | |
parent | a707ab5f345f70ce92eb6cc92a46838654c0225d [diff] |
app.yaml: Increase CPUs Increase to 8 CPUs to increase parallel performance. BUG=chromium:793042 TEST=None Change-Id: I63837bc594ac088280bd9e611602ec95d032043f Reviewed-on: https://chromium-review.googlesource.com/953328 Commit-Ready: Paul Hobbs <phobbs@google.com> Tested-by: Paul Hobbs <phobbs@google.com> Reviewed-by: Paul Hobbs <phobbs@google.com> Reviewed-by: Ningning Xia <nxia@chromium.org>
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_bot credentials.
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.
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”.