doc: Mention Buildkite in the hacking document

Includes link to the Buildkite SSO login, which is currently not visible anywhere else in documentation. Change-Id: Ic3ec6412127b2ac0df7e6efc4ec6020cc9d8b34f
2025-10-15 09:21:49 +00:00
parent faa0b4f291
commit 30a5f8ec15
1 changed files with 8 additions and 0 deletions
@@ -170,6 +170,14 @@ Once you get a `Code-Review+2` vote on your change, it's rebased on `main` and C
 If the change appears as "Rebase Required", you need to rebase it on `main` locally or via the Gerrit UI and wait for `Verified+1` before the Submit button is made active
 The `Code-Review+2` from before will stick around through trivial rebases so no need to re-request review for a mere rebase.

+## Interacting with the CI, Buildkite
+
+We use Buildkite for our CI, usually you will not have to interact directly with it other than reviewing any errors it produces, which are linked from Gerrit.
+
+However in certain cases a CI run will fail due to transient issues not related to your code and you will need to rerun it by hand.
+You can log in to the CI via [SSO](https://buildkite.com/sso/lix-project). On your job you can then hit the "Retry failed" button to rerun it, normally you will not have a repeat of the transient issue.
+If the build still fails on CI issues or all builds are failing this should be reported via [Zulip on #T-infra](https://zulip.lix.systems/#narrow/channel/7-T-infra) or [Matrix on #dev](https://matrix.to/#/%23dev%3Alix.systems?via=lix.systems).
+
 ## Building Lix with `nix`

 To build a release version of Lix for the current operating system and CPU architecture: