Journey of Automation - Github, Galaxy, Fedora
summary
Repository release is automated end to end: a script collects merged PRs, uses conventional commits on PR titles to compute the next semantic version and assemble a changelog, pushes a changelog PR, then a GitHub workflow creates a git tag and GitHub Release and publishes the Ansible role/collection to Ansible Galaxy. Fedora packaging flows use packit propose-downstream to open dist-git PRs, trigger Koji builds and Bodhi updates with one manual maintainer merge; gaps (spec file ownership, concise changelog entries, multi‑source Source updates) are solved with custom GitHub actions and a spec fetch hook.
AI-written summary · about
chapters (5)
- 0:00Linux System Roles intro
- 1:03GitHub to Galaxy automation
- 5:28Fedora RPMs with Packit
- 7:35Packit automation challenges
- 11:30Conclusion & Q&A
related talks
18mDeveloper Workflow Automation with GitHub Actions (CI/CD)
14mUsing packit and testing farm for CI/CD and automation in an upstream project
31mRelease it like a pro!
20mStreamlining Release Management for DevOps Success
24mAuto - maintain your Package
02h 59mCI/CD with Github Actions
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
45mLet's automate one more thing