You can interact directly with your builds by connecting to the runner over SSH. This is helpful for troubleshooting your manifests, or just getting a quick temporary environment to test something in.

When a build fails, the VM stays alive for an extra ten minutes, and you'll be presented with instructions on how to connect to the runner via SSH, e.g.:

$ ssh -t builds@azusa.runners.sr.ht connect 81809
Connected to build job #81809 (failed):
https://builds.sr.ht/jobs/~sircmpwn/81809
Your VM will be terminated 4 hours from now, or when you log out.

bash-5.0 $

In addition to connecting to failed builds over SSH, you can add shell: true to your manifest to always enable SSH access. Then, you'll be able to interact with your build as it runs.

About this wiki

commit a587053d94365eca00c57a74185dd4b2fe0c99c1
Author: Jarkko Oranen <oranenj@iki.fi>
Date:   2020-10-21T20:26:23+03:00

OpenBSD 6.8 released, update compatibility docs accordingly
Clone this wiki
https://git.sr.ht/~sircmpwn/sr.ht-docs (read-only)
git@git.sr.ht:~sircmpwn/sr.ht-docs (read/write)