Can confirm, Forgejo also has actions that are compatible with github actions.
I just started using that a little bit recently.
Gitea does too.
No reason to stay on github anymore.
my only reason is that big projects use github and so does majority of everyone. altho the switch to gitlab or codeberg is seen in many FOSS projects , it’s not 100% there yet… i recommend playing safe having accounts on all platforms for the time being
The ecosystem. With GitHub you add 10 jobs with a single “using” line and be done with it, with GitLab you manually download 10 binaries, install them, then write scripts to use them, then ensure the binaries and their cache locations are properly cached, then run cleanup steps if you’re responsible.
It’s a compromise even if its not a deal breaker.
if you are downloading the tools in every pipeline run, you are doing it wrong, wasting resources and time. tools should be baked into a new docker image that you use in the pipeline. another pipeline updates the image on schedule
Real answers: gitlab has awesome integrated CI, and you can always go for a remote integration if you prefer (e.g. self-hosted Jenkins, or a managed solution like circleci).
Real Questions, is there a competitor that offers the same feature set? Last I looked no one had anything to compete with github actions.
GitLab exists and is used by many big corpos already, and Codeberg has its own version of Actions (woodpecker I think it’s called.)
woodpecker was an older system, it supports github actions workflows too
gitlab and codeberg…gitlab is partially open source but codeberg is fully opensource
Codeberg is based on the software Forgejo, just with some extra modifications. I’m running my own Forge instance and it’s absolutely great
Can confirm, Forgejo also has actions that are compatible with github actions. I just started using that a little bit recently. Gitea does too. No reason to stay on github anymore.
my only reason is that big projects use github and so does majority of everyone. altho the switch to gitlab or codeberg is seen in many FOSS projects , it’s not 100% there yet… i recommend playing safe having accounts on all platforms for the time being
Cicd is pretty replaceable for any workflow regardless of platform. What’s the killer feature of actions for you?
The ecosystem. With GitHub you add 10 jobs with a single “using” line and be done with it, with GitLab you manually download 10 binaries, install them, then write scripts to use them, then ensure the binaries and their cache locations are properly cached, then run cleanup steps if you’re responsible.
It’s a compromise even if its not a deal breaker.
if you are downloading the tools in every pipeline run, you are doing it wrong, wasting resources and time. tools should be baked into a new docker image that you use in the pipeline. another pipeline updates the image on schedule
I’m really interested in an example of this.
Real answers: gitlab has awesome integrated CI, and you can always go for a remote integration if you prefer (e.g. self-hosted Jenkins, or a managed solution like circleci).