FreeBSD CI revival
After a chat with @chreekat, @Mikolaj and @maerwald, it has become clearer that we should be able to revive the FreeBSD CI progressively.
Currently the things to take into account are:
- OS Availability
- OS Expertise
- Trusted Runners for release builds
OS Availability
Cirrus CI provides FreeBSD runners that we can use without having to configure them ourself. The QEMU project has an explained setup for such an integration in GitLab: https://github.com/qemu/qemu/tree/master/.gitlab-ci.d/cirrus
OS Expertise
Today we have the help of @arrowd to orient us on some matters. I think reaching out to the FreeBSD Foundation (from the Haskell Foundation) one day might prove useful to get some relationship going.
Trusted runners
It is my understanding that we want to have our own runners for release builds. Cirrus CI wouldn't cover this requirement, but it is not necessarily a problem if we provide a tarball that is well-suited for downstream vendors (Distributions, ghcup) to run the tests themselves and generate a binary. At least it's not a problem now.
Comments welcome.