|author||Paul Hobbs <firstname.lastname@example.org>||Tue Nov 21 00:25:31 2017|
|committer||Paul Hobbs <email@example.com>||Tue Nov 21 00:28:36 2017|
Deploy_app: allow deploying other yaml files TEST=Used it BUG=chromium:756762 Change-Id: I27f861d28acf6c457d1e440ecfe358bc0d327135
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”.