Is it really that low an impact? A lot of the work performed in CI is duplicated (`apt update && apt install texlive-full` f.ex.), and thus there'd be a benefit to running it less often.
> Automated CI systems, large-scale dependency scanners, and ephemeral container builds, which are often operated by companies, place enormous strain on infrastructure.
> These commercial-scale workloads often run without caching, throttling, or even awareness of the strain they impose.
I personally expected the AI stuff to be a fad that would go away quickly, and thus didn't get out the second they did that (for the same reason that distro-hopping is unhealthy). It's more a symptom of the frog recognising that okay yeah the temperature's grown definitely too high.
Yes, but you are still not allowed to use them for proprietary software development. That makes it quite useless for most teams developing commercial software.
Actually, that's only for the Woodpecker instance. Forgejo Actions can be used without asking for permission, and three tiers of (Linux-only, adm64-only) free runners are provided.
Consider also https://openssf.org/blog/2025/09/23/open-infrastructure-is-n... :
> Automated CI systems, large-scale dependency scanners, and ephemeral container builds, which are often operated by companies, place enormous strain on infrastructure. > These commercial-scale workloads often run without caching, throttling, or even awareness of the strain they impose.
...which implies that the load isn't negligible.