Discussion
Today's recreational computer touching will include setting up a NetBSD CI machine for #iocaine.
Since there's no forgejo runner in pkgsrc as far as I can tell, nor any other CI runner that could report to Forgejo, I'll spin up a VM, and use actions/bsd1 to SSH in and run commands.
A custom action I will be writing today. ↩︎
I will, of course, have to name the NetBSD VM, and I recently started to name things after plants, using their latin name.
For many reasons, I'm gonna name the VM after some kind of moss. I just need to find the proper latin name.
I think I'll be going with Andreaeaceae, for two reasons:
VM image prepared and copied to Luggage. Initial attempt at starting the VM on boot, via declarative config is currently being deployed.
If that works, I'll write the actions/bsd action, and see if it works.
VM is up and running, now to write the actions/bsd thing.
Ideally, I'll want to do something like...
jobs:
netbsd:
runs-on: nixos-latest
steps:
- name: checkout
uses: actions/checkout@v6
- name: build
uses: actions/bsd
with:
host: andreaeaceae
run: cargo build
This would:
bin/shI'll have to update my VM to share forgejo-runner's workdir, and fix up UIDs and stuff.
Also, forgejo runner will need to have access to the SSH privkey.
Install bonfire.cafe
Get the full app experience