builds.sr.ht image maintenance
Published:
Documentation is available, and the process itself is not difficult; if you want to update an image you just have to follow instructions.
There was one aspect of the process that had me a bit confused. Namely, testing the new image. What exactly constitutes a test?
To test new versions, create a clone of builds.sr.ht with the patch applied on git.sr.ht, then update your image's build.yml file to point to your git repository, and remove the deploy task. Submit this build to builds.sr.ht to test-build your new image version from an earlier version which is already available, and address any problems that arise during testing.
I am not the sharpest tool in the shed, so it was not immediately evident from the above text what exactly I should do.
It is clear that I have to have a patched copy of the repository, and that I have to submit a build on builds.sr.ht to see if the image will be successfully built.
What is less clear is how changing the build.yml of the image I
want to push will trigger the build.
From my understanding of Sourcehut's documentation, and my experience with
the system, only builds defined in the .builds directory in the
root of the repository are submitted by a push to a repository.
Maybe it is a hut thing?
I ended up replacing the
.builds/alpine.yml
with
images/openbsd/build.yml,
removing the deploy task (as the documentation says one
should), and pushing the code.
Et voilà!
I got a successful build.
The only things left to do were to post the patches to the ~sircmpwn/sr.ht-dev mailing list. The patch adding OpenBSD 7.8 image has been accepted, so I guess my understanding of the documentation had been good enough. I consider this a wholly acceptable outcome.
Anyway, you can now build your projects using the openbsd/7.8
image.
Next: Installing OpenBSD on QEMU
Previous: Van Helsing (2004)