2026-09-13 –, D.0.02
In June 2026, the FreeBSD entries in dozens of upstream .cirrus.yml files became dead code. For roughly five years, Cirrus CI had been doing; almost invisibly; what FreeBSD's own internal CI was never designed to do: making it trivial for upstream open-source projects (LLVM, Rust, Python, PHP, Node.js, libuv, curl, and others) to test their software against FreeBSD on every pull request, with no infrastructure for them to operate. That capability is now gone. Nothing in the current market replaces it.
This talk argues that FreeBSD's adoption ceiling is set by whether upstreams can test on FreeBSD; not just by whether we can test FreeBSD ourselves. It works through four threads: what Cirrus quietly solved between 2019 and 2026, and why most of the community didn't notice; the current landscape of partial substitutes (vmactions/freebsd-vm, self-hosted Jenkins, the GitHub Actions BSD gap, the in-tree pre-commit tooling) and why none of them fits the shape of the upstream-facing problem; why no individual developer can plug this gap, and why this is a company-scale problem rather than a hobby one; and what FreeBSD is already paying for the absence; in enterprise procurement conversations, contributor attrition, and quiet drop-outs in upstream release notes.
The talk closes with a five-point specification for what a viable successor would have to look like, and asks three groups in the room for specific action: the FreeBSD community, the Foundation and enterprise users, and the upstream maintainers themselves.
Forty minutes; five for questions. Technical, opinionated, assumes the audience knows what make buildworld does.
Moin is a FreeBSD infrastructure developer working with the FreeBSD Foundation. His focus areas include CI/CD pipelines, reproducible builds, secure artifact delivery, release engineering, and cluster administration. With a strong operational background, he helps maintain critical infrastructure that supports FreeBSD’s development, testing, and release processes.
He has been deeply involved in packaging and ecosystem health within the FreeBSD project; especially the Ports Collection; advocating for higher standards in quality, lifecycle management, and risk awareness. His contributions span both code and community discussions, particularly around supply chain security, port deprecation policy, and the need for modern auditability in a rapidly evolving threat landscape.
Through both hands-on maintenance and policy-level insight, he continues to push for a Ports Collection that balances flexibility with responsibility and meets the needs of today’s security-conscious users.