Building for Enterprise by Testing OSS: One Codebase to Rule Them All
summary
One codebase generates and tests packages across Ubuntu 16.04/18.04/20.04/22.04 and RHEL variants, for x86 and ARM, producing DEBs, RPMs, tarballs, snaps and Docker images; tooling uses fpm to build packages, Jinja to generate Dockerfiles and service configs, pytest for marker‑driven cross‑OS tests and GitHub Actions plus act and qemu for local emulation. CI signs artifacts with GPG and handles macOS notarization quirks. The pipeline publishes nightly images to Docker Hub and is actively used, with Apple signing and Docker manifest changes as the main pain points.
AI-written summary · about
chapters (16)
- 0:00Introduction and background
- 3:09Enterprise packaging challenges
- 7:00Building reproducible packages
- 10:11Automating with Python and tools
- 13:18Pain of manual packaging
- 16:26Templating with Jinja2
- 18:34Security and code signing
- 23:07Layered testing approach
- 25:15Pi test framework benefits
- 26:57Enterprise testing integration
- 31:52Open source testing philosophy
- 34:19Local testing and CI trade-offs
- 36:25Version pinning pitfalls
- 37:51Refactoring and patterns
- 41:21Tooling and OS choices
- 42:47Q&A session
related talks
45mSponsored Session: Because Security Matters: Securing Your Open Source Supply Chain
32mSoftware Supply Chain with the Yocto Project
50mMastering Modern Software Distribution: On-Prem, Air-Gapped, and BYOC Challenges
23mBuilding Secure Package Pipelines
14mUsing packit and testing farm for CI/CD and automation in an upstream project
20mSponsored Demo: Secure, Portable, Operable: A Strategy for Modern Services
24mIntroducing OSBuild
46mThe Software Factory