-- Anzeige/Ad --
A piece of criticism to all code forges I know: why not run #CI on all commits?
A bad commit is a liability. It will break bisect and make debugging miserable.
#ForgejoActions takes it to the extreme and cancels an already running action when I push another change.
I get it - it's too slow and expensive to test them all when pipelines take minutes to run. But you could just pause the old ones until the newest one is finished!
dorotaC
Als Antwort auf dorotaC • • •Oh, now I realized: most forges host underpriced runners, so they have a reason to have them run as little as possible.
Well, I set up my own runner on #forgejo for a single repo, so I have power to spare 😛
Codeberg.org
Als Antwort auf dorotaC • • •It's also not a wise move w.r.t. to energy consumption, environmental impact, and the best way to accelerate #climatecrisis. Also read wimvanderbauwhede.codeberg.pag…
So following Pareto principle, you want to find a sweet spot between energy consumption and code checks.
Even if I had the money, I would still reduce pipelines to a bare minimum to avoid wasting energy.
~f
Frugal computing • Wim Vanderbauwhede
wimvanderbauwhede.codeberg.pagedorotaC
Als Antwort auf Codeberg.org • • •@Codeberg
If your pipeline takes 2 minutes and saves 2 hours in debugging and another 20 in working around the problem at the end user side - which is the case at least for me - then the sweet spot is quite clear.
> the best way to accelerate #climatecrisis
I call this a ridiculous statement. If running a computer for 5 extra minutes is comparatively so bad, we should reconsider software altogether.
There are many better ways to heat up Earth, related to transportation and manufacturng.