cicada VS gitea

Not sure if related, but recently read about https://github.com/Cicada-Software/cicada which looks like to abstract GithubCI and GitlabCI.

LICENSE AGPL

https://github.com/Cicada-Software/cicada/blob/main/LICENSE

I.. wouldn't use to build commercial software.

I'm guessing it's this: https://news.ycombinator.com/item?id=35364146 although it didn't seem to get much traction other than the one comment that matches what I found while trying to read up on it:

https://github.com/Cicada-Software/cicada/blob/main/docs/ci-...

> create a file _anywhere in your repository_ ending in .ci

uh-huh

> Note that you cannot use the pipe operator (|) with the shell command, only one command can be executed at a time

uh-huh

> To make sure that your workflow works, try pushing to your repository

so, no local runner for this, either. fantastic.

So instead of using Starlark, which a non-trivial number of folks already know, there's already editor support for, and is obviously designed to be embedded, they decided that what the world needs is another DSL. Got it.

Hi HN! My name is Logan Hunt, and I am the founder and CEO of Cicada. Cicada is a self-hostable CICD platform that integrates with GitHub and Gitlab, allowing you to write workflows without caring about the underlying implementation details of the platform you are using. Source code (AGPL-v3 licensed) is available here: https://github.com/Cicada-Software/cicada and the live site is available here: https://cicada.sh

With Cicada you build automation workflows using our custom DSL (domain specific langauge), built specifically for writing automation workflows. The Cicada DSL is a fully functional programming language, meaning you can use variables, if statements (coming soon!), and execute shell commands without having to write a single line of YAML. And, best of all, these workflows can work with GitHub and Gitlab without any modifications.

One of the best parts of GitHub Actions (IMO) is the ability to easily trigger workflows from many types of events such as git pushes, opening/closing pull requests, or creating a new release. With Cicada you will be able to fire off workflows for all of these events, no matter what platform you choose. Say good by to vendor lock-in!

Having used GitHub Actions, Gitlab CI, and Azure DevOps at my previous job, I found that these tools where good at describing basic automation tasks, but failed whenever you wanted to do something complex. In addition, these platforms all use YAML for configuring their workflow files, which means you need to write a shell script for anything more complex than basic linting or testing. Another inherent problem with these solutions is that they all use different YAML formats, making them incompatible with one another, further locking you in to their platform. Cicada solves that by making a single, unified format that works no matter what platform you use, and converts all the platform-specific events types into one platform-agnostic type. This means that a git push event coming from GitHub will look identical to a git push event coming from Gitlab.

Cicada is in the early stages right now. A working MVP is up and running, but it is far from complete. I've been holding off open-sourcing Cicada until later, but given the recent GitHub outages this week, I felt this would be the perfect time to do an initial "launch".

Currently Cicada is running on a small Linode server, and the workflows are ran using Docker. I've removed the white-list so anybody can run workflows for the time being, though I expect it will get swamped rather quickly, in which case I will re-add the white-list. Also, getting GitHub permissions right is hard, so for the time being, you must push to GitHub repositories that are on your personal account (and are an owner of).

Let me know what you think!

Gitea - Another self-hosted Git service. [Git]

You can both be right. The title as it stands describes Codeberg as a "Fast Open Source Alternative to GitHub" and I'd agree that it's a confusing title to say the least.

What we're really talking about here is a free-as-in-beer SaaS service that primarily caters to open source software repositories. This isn't clear in the title, because "Open Source" in this context can be read both as the back-end itself being open source (which it is), or more correctly -- but much less obviously -- that it's an alternative for open source repositories compared to GitHub.

Codeberg uses Forgejo[1] which in turn is a soft fork of Gitea[2], and anyone can use these two projects to self-host their proprietary codebase -- but the title for this post in no way makes it clear what Codeberg actually is.

One could literally just take the first thing you see on their website and it would be a much better description:

> Codeberg is a collaboration platform and Git hosting for free and open source software, content and projects.

[1]: https://forgejo.org/

[2]: https://github.com/Codeberg-org/gitea