561
edits
(Wrap all the console commands inside source tags) |
(→Administration: Update config update steps for new buildbot.) |
||
Line 54: | Line 54: | ||
sudo -s | sudo -s | ||
/etc/init.d/buildslave stop | /etc/init.d/buildslave stop | ||
/etc/init.d/ | /etc/init.d/buildmaster stop | ||
cd ~buildbot/buildbot | cd ~buildbot/scummvm-sites | ||
git pull | sudo -u buildbot git pull --ff-only | ||
/etc/init.d/ | /etc/init.d/buildmaster start | ||
/etc/init.d/buildslave start | /etc/init.d/buildslave start | ||
</source> | </source> | ||
If problems arise, check if all files in the master (~buildbot/master) and slave (~buildbot/slave) directories are owned by the correct user (buildbot: | If problems arise, check if all files in the master (~buildbot/scummvm-master) and slave (~buildbot/scummvm-slave) directories are owned by the correct user (buildbot:buildbot). If the daemons were incorrectly started, new files might have been created under another user account. In that case: | ||
* stop the daemons (see above) | * stop the daemons (see above) | ||
* fix the permissions with | * fix the permissions with | ||
<source lang="bash"> | <source lang="bash"> | ||
chown -R buildbot: | chown -R buildbot:buildbot ~buildbot/scummvm-master/* | ||
chown -R buildbot: | chown -R buildbot:buildbot ~buildbot/scummvm-slave/* | ||
</source> | </source> | ||
* start the daemons | * start the daemons |
edits