Ever wondered what can be done for automating Fedora packaging? In this case Ruby Gems packaging. I've created the tooling to update, monitor, test, and push updates in to Fedora, all in an collaborative way (PRs).
What simply started as a way to repeat identical tasks became set of tooling. Although individual tools are highly configurable, all are written with a specific purpose in mind (do one thing well), and can run in an automated way. I've set those up to run on all Fedora rubygem packages, therefore helping with automating package updates (well, apart from the conflicts...). While also doing some proactive testing with packages yet to be updated.
I'll introduce the general approach, and how the respective tools are integrated. I'll briefly describe specific toolings use-cases, show demo of the tooling altogether, and workflow for resloving conflicts.
All tools are CLI based, standalone, and minimalistic. If a part of it seems unfit, it can be easily re-written (or replaced with other tool), therefore "The Prototype".
Video Stream