Confirmed users
1,351
edits
ReleaseEngineering/Applications/Bumper: Difference between revisions
ReleaseEngineering/Applications/Bumper (view source)
Revision as of 23:49, 28 January 2016
, 28 January 2016Add deployment instructions.
m (add header) |
(Add deployment instructions.) |
||
| Line 18: | Line 18: | ||
b2g_bumper runs on buildbot-master66.bb.releng.usw2.mozilla.com (see /etc/cron.d/run_b2g_bumper) | b2g_bumper runs on buildbot-master66.bb.releng.usw2.mozilla.com (see /etc/cron.d/run_b2g_bumper) | ||
==== How is bumper deployed? ==== | |||
Deployment is semi-automated: | |||
* Code should first be landed on the default branch, and pushed. | |||
* Monitor #releng for a success message from travis-ci | |||
** If you don't see a success or fail message within 10 minutes, something is very wrong (e.g. syntax error). | |||
*** Be sure each of the applications scripts and config files can be imported successfully: | |||
cd scripts | |||
PYTHONPATH=.. python -c 'import b2g_bumper' | |||
cd ../configs/b2g_bumper | |||
for f in *py; do python $f; done | |||
* After the success message is seen for default branch, merge to production and push: | |||
hg checkout production | |||
hg merge default | |||
hg commit -m 'merged default->production; tests passing' | |||
hg push | |||
* The new version will be used the next time b2g_bumper executes. That may be in advance on the travis-ci report on the production branch. | |||
==== Troubleshooting ==== | ==== Troubleshooting ==== | ||