Skip to content

Commit

Permalink
Add docs on restarting the buildbot
Browse files Browse the repository at this point in the history
  • Loading branch information
boomanaiden154 committed Oct 17, 2024
1 parent a23efbf commit a687e33
Showing 1 changed file with 26 additions and 0 deletions.
26 changes: 26 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,32 @@ If a unit test failed, this is shown below the build status. You can also expand
the unit test to see the details: ![unit test
results](docs/images/unit_tests.png).

# Restarting Buildbots

Restarting the buildbots can be accomplished be deleting the pods running the
buildbots. Kubernetes will automatically recreate the pod, essentially
performing a restart.

To find the name of the buildbot pod, first make sure you are using the correct
cluster configuration with `kubectl` as the windows and linux builders are on
separate clusters.

Then, find the name of the buildbot pod:

```bash
kubectl get pods | grep buildbot
```

Once you have the name of the pod, you can run the following command:

```bash
kubectl delete pod <pod name from previous step>
```

This command might take a couple minutes to execute as kubernetes stops
the running processes/container. The new pod will then spin up and
everything will hopefully work after the restart.

# Contributing

We're happy to get help on improving the infrastructure and workflows!
Expand Down

0 comments on commit a687e33

Please sign in to comment.