eliott/servo
1
0
Fork 0
mirror of https://github.com/servo/servo synced 2026-04-25 17:15:48 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated Buildbot administration (markdown)

Lars Bergstrom
2016-04-05 14:24:43 -05:00
parent 5681ccc055
commit ae409d8d49
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Buildbot-administration.md

@@ -140,7 +140,7 @@ Always verify the changes to be applied with
# salt servo-master1 state.highstate test=True
```
Then, if homu is not running anything, update all the machines with:
If the changed services do not include buildbot OR buildbot is not currently running a job, you can update with:
```console
# salt servo-master1 state.highstate
```
@@ -165,7 +165,7 @@ in the user's fully qualified IAM ID, which looks like
# Dealing with troubles
If homu is not picking up changes in state for PRs properly, you can do:
If homu is not picking up changes in state for PRs properly, you should first click the Synchronize button in homu for the repo. If that does not work, homu may be restarted by doing:
```console
# service homu restart
@@ -188,8 +188,6 @@ WITH EXTREME CAUTION, if the buildbot master appears to be in a very bad state,
# service buildbot-master restart
```
If there are any EC2 instances connected, make SURE to use the "graceful shutdown" button. This button will cause the EC2 instance to shut down correctly and be restarted once buildbot comes back. If you do NOT do this, the latent instance will hang around, fail to connect to the buildbot, and require admin intervention to clean up.
# Handling low disk space
There is a scheduled job to delete logs over 5 days old each night on each builder,