home tags events about login
one honk maybe more

benjojo posted 07 Sep 2026 16:48 +0000

New found sympathy for the GitHub actions ops people after setting up and running everything via a Forgejo CI runner, like damn this workload sucks it churns [CPU/Disk Wear] like crazy

benjojo replied 07 Sep 2026 17:19 +0000
in reply to: https://mastodon.social/users/jamesog/statuses/117230891072682402

@jamesog Just a lot of CI runs are not optimised to be nice (github actions kind lets you be messy because you don't feel the consequences)

But the real nasty stuff is dealing with jumbo jobs (like kernel builds) with concurrent "boring builds", and then there are more questions around if caches help or hurt your build times, etc

icedquinn@blob.cat replied 08 Sep 2026 10:41 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/jSw97g8vMc24hVB9D4

@benjojo CI tools in the field are truly a horror.

laminar with something like apptainer is pretty nice. you write a bash script that builds the environment, apptainer runs it to make a single squash file, have the laminar job do a clone and call the apptainer to build it. laminar has workspaces so you can recycle a repo and just do a cheap 'git pull' on it. nice

the mind boggles how many resources are wasted by things like "standard github ubuntu image, downloads one or more binaries from the internet every build run, does a full checkout for some reason for one build run"

concourse is kind of a nice CI system but its lack of kube support is sort of pushing it behind. but concourse also supports some kind of at least diff pulling.

the amount of repeated wget + git clone has to be something even please.build gives me pause (hermetic build involves copying only named files in to the sandbox; which COULD be cheap reflinks, or COULD be FUSE, but it is not FUSE and i'm not entirely sure if its reflinks.)

i try not to think about it all