Get the latest tech news
Tracking Releases and CI Across Software Teams and Forges
A walkthrough of a simple release & CI tracking system I built for keeping track of the various teams I manage at Canonical using a small Go application, Hugo and Github Actions
I did maintain a Jekyll version for some months, but my lack of (recent) familiarity with the Ruby & gems ecosystem was making updates and maintenance more tedious than I liked. I created a workflow which is triggered every hour to dump the latest report using releasegen, regenerate the Hugo site, and commit the outcome to branch of the repo which is used to serve the page. I have an idea about how to generalise the processing of data, which would both remove my reliance on the Github API, and also unify the approach for gathering information about Git repos across forges (making it easier to support the likes of Codeberg and Sourcehut).
Or read this on Hacker News