Hacker News Reader

Comment by cowlevel | Hacker News Reader

gitea, forgejo, gitlab CE, and ssh still working fine

I never noticed downtime with public GitLab. It's also generally better than GitHub and Actions.

A self-hosted enterprise GitLab instance in Azure, on the other hand, has had outages and performance degradation quite a few times.

I have to second this, GitLab CI is pretty good. I'll never be on board with infrastructure people's obsession with putting code in yaml but outside of that, the model makes much more sense to me.

A GitLab runner is a machine/VM which can get notified of a GitLab CI job, then run the job's container image (downloading it from GitLab's container registry if necessary), then run the code in the yaml file. You get to control your build environment.

It's so weird that GitHub Actions's model is "have one absolutely gigantic container image which contains everything any build could ever need, and if something's missing, the documented answer is to apt install it every run".

Of course. Azure is the reason GitHub is down so often, too.

Exactly. I'm running forgejo in a container, pushing backups to a private S3 storage, and sent the forgejo team a small liberapay payment.

Maybe 30 minutes to get it all setup and then I moved on with my life.

What are you using for CI on your forgejo instance? Are there any popular "turn key" solutions out there?

Currently, I am doing firmware development for my clients, so I do not have a CI pipeline. I'm doing build, test, flash manually on the bench.

(about to be hit with rotten vegetables by the purists...)

ah this is what I do too, I understand there are things like woodpecker but wish there was just some community docker image that handles this all for you.

Reply on news.ycombinator.com