Confirmed users
1,364
edits
ReleaseEngineering/How To/Restart BuildAPI: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Restart BuildAPI (view source)
Revision as of 02:25, 11 February 2017
, 11 February 2017correct which directory to be in when restarting app, and compute current build #
(update with lessons learned on 1338720) |
(correct which directory to be in when restarting app, and compute current build #) |
||
| Line 24: | Line 24: | ||
if you want to just restart buildapi (you don't want to update or use a newer version). The following will sync the code out to the web nodes and cause a restart (since ``production.ini`` is modified) | if you want to just restart buildapi (you don't want to update or use a newer version). The following will sync the code out to the web nodes and cause a restart (since ``production.ini`` is modified) | ||
<pre> | <pre> | ||
# cd /data/releng/src/buildapi | |||
# echo "# <user> restarting bug XXXX" >> production.ini | # echo "# <user> restarting bug XXXX" >> production.ini | ||
# / | # ./update buildapi $(pip freeze | grep buildapi | sed 's,[^0-9]\+,,') | ||
</pre> | </pre> | ||
You'll know that buildapi has been restarted if you see the following output reported for all web hosts: | You'll know that buildapi has been restarted if you see the following output reported for all web hosts: | ||