24
edits
Difference between revisions of "Buildbot"
Jump to navigation
Jump to search
buildbot administration
(→Status: Update: SVN->GIT, new location for nightlies) |
(buildbot administration) |
||
| Line 46: | Line 46: | ||
If your toolchain/port is ready to be added, ask ''sev'', ''joostp'' or ''dhewg'' for an account. | If your toolchain/port is ready to be added, ask ''sev'', ''joostp'' or ''dhewg'' for an account. | ||
== Administration == | |||
When the buildbot config files are changed, a user with shell access and sudo privileges needs to run the following commands. It's good practice to do this once buildbot is idle: | |||
sudo -s | |||
/etc/init.d/buildslave stop | |||
/etc/init.d/buildmaster stop | |||
cd ~buildbot/buildbot | |||
svn up | |||
/etc/init.d/buildmaster start | |||
/etc/init.d/buildslave start | |||
If problems arise, check if all files in the master (~buildbot/master) and slave (~buildbot/slave) directories are owned by the correct user (buildbot:nogroup). If the daemons were incorrectly started, new files might have been created under another user account. In that case: | |||
* stop the daemons (see above) | |||
* fix the permissions with | |||
chown -R buildbot:nogroup ~buildbot/master/* | |||
chown -R buildbot:nogroup ~buildbot/slave/* | |||
* start the daemons | |||