I've recently switched my CI/CD setup to a self-hosted Gitea runner due to concerns about GitHub runner pricing and data privacy. I set up Gitea on Docker and found that Gitea Actions is compatible with existing GitHub Actions .yaml files, so I didn't have to rewrite my pipelines at all! It's currently running on my home server with no cost, zero cold starts, and complete data privacy. I'm wondering if anyone else has experience running Gitea Actions for actual production workloads and how well it scales.
6 Answers
Is it possible for Gitea Actions to integrate with GitLab? What do you think?
Exactly! You could potentially mirror or clone repositories from outside, but I'm not sure about shared authentication unless you set up SSO or reuse SSH keys.
I've been using Gitea Actions since its launch and have had a smooth experience with no major issues so far.
Why did you choose to migrate the whole repository instead of just using another CI/CD tool?
Actually, I just moved my CI setup, not the entire repo.
We’ve been using Gitea Actions for a small production team for over a year now, and we had to upgrade to a large AWS EC2 instance to handle intensive testing. Gitea doesn’t need much power, which helps keep costs down.
I manage my home network and use Terraform for personal Azure resources. I deploy changes through a self-hosted runner and that costs about $4 a month—still manageable. I think this year could be huge for Gitea!
Why not go with GitLab?
GitLab tends to be resource-intensive compared to Gitea.
It's not a silly question! Unfortunately, Gitea doesn't have native compatibility with GitLab. It would be neat if it did, though.