Confirmed users
502
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 23:37, 26 January 2015
, 26 January 2015adds instructions on how to restart buildapi web app without pinging webops
(→Redis) |
(adds instructions on how to restart buildapi web app without pinging webops) |
||
| Line 6: | Line 6: | ||
= Restarting the buildapi web app = | = Restarting the buildapi web app = | ||
You can ask webops as they know how to do it. However, since we have root privs on relengwebadm, this can be done self serve. | |||
some background: 'relengwebadm' hosts a number of releng apps. you can see them under '/data/releng/www/*'. There is a shared deploy/restart script here '/data/releng/deploy'. You can run this script on its own and it will update each app in www/ or you can pass in an individual app (e.g. buildapi), and it will deploy/restart against the latest known version. Depending on the app, the version may be stored in puppetagain or somewhere else. For buildapi, it's in puppetagain repo. | |||
first: | |||
<pre> | |||
$ ssh $LDAP_SHORTNAME@relengwebadm.private.scl3.mozilla.com | |||
$ sudo su - | |||
</pre> | |||
then decide: | |||
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: | |||
<pre> | |||
# /data/releng/deploy buildapi | |||
</pre> | |||
or if you want to update buildapi against a new version and deploy: | |||
* https://wiki.mozilla.org/ReleaseEngineering/BuildAPI#Updating_code | |||
= Restarting the agent = | = Restarting the agent = | ||