5 ms·

I’m trying to migrate my personal repos from GitHub to Codeberg. The biggest challenge is to find a replacement for GitHub Actions (the free offering is so gene

I’m trying to migrate my personal repos from GitHub to Codeberg. The biggest challenge is to find a replacement for GitHub Actions (the free offering is so generous), and my current solution for that is to self-host an instance of Woodpecker CI [1]. I’d like to see even more diversity in Git hosting beyond “let’s all migrate from X to Y”, and for that to happen, Forgejo (the soft fork of Gitea that Codeberg runs) has already begun to implement federation [2], which can make cross-instance collaboration easier. [1]: http://woodpecker-ci.org/ http://woodpecker-ci.org/ [2]: https://codeberg.org/forgejo/forgejo/issues/59 https://codeberg.org/forgejo/forgejo/issues/59

chrisweekly 4y ago
GitLab CI is pretty good.
tough 4y ago
This was on HN past week https://cicada.sh/ https://cicada.sh/
- mdaniel 4y ago
  I'm guessing it's this: https://news.ycombinator.com/item?id=35364146 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-lang/getting-started.md#your-first-workflow 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.
RamblingCTO 4y ago
They (Gitea) introduced actions. It is already included in the current releases, but codeberg might just not activate it. It works quite good, I actually wrote a gitea action already ("gitea-release-drafter").
- hakre 4y ago
  Nice, perhaps is worth to invest into such kind of "fediverse" (using Codeberg with my own hosted action runners/boxes), I'd buy into that feature much faster than into any other (e.g. using Codeberg for PRs from proprietary hosted "Codeberg" instances).
  - RamblingCTO 4y ago
    There's also work on that ;) the dude doing most of the work moved to forgejo and some parts are already implemented but I'm not sure what the state is. I would also love to see federation, that's what would really be a github killer and drive this ecosystem forward imho. - https://github.com/go-gitea/gitea/issues/18240 https://github.com/go-gitea/gitea/issues/18240 - https://codeberg.org/forgejo/forgejo/issues/59 https://codeberg.org/forgejo/forgejo/issues/59
- kotatsuyaki 4y ago
  Glad to see new options. I wonder if Codeberg is going to enable actions, given that they’ve already setup an experimental instance of Woodpecker that can be requested [1] on a per-user basis. [1]: https://codeberg.org/Codeberg-CI/request-access https://codeberg.org/Codeberg-CI/request-access
xvilka 4y ago
SourceHut[1] has CI out of the box[2]. [1] https://sourcehut.org https://sourcehut.org [2] https://man.sr.ht/tutorials/getting-started-with-builds.md https://man.sr.ht/tutorials/getting-started-with-builds.md

chrisweekly 4y ago

GitLab CI is pretty good.

tough 4y ago

This was on HN past week https://cicada.sh/ https://cicada.sh/

mdaniel 4y ago
I'm guessing it's this: https://news.ycombinator.com/item?id=35364146 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-lang/getting-started.md#your-first-workflow 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.

RamblingCTO 4y ago

They (Gitea) introduced actions. It is already included in the current releases, but codeberg might just not activate it. It works quite good, I actually wrote a gitea action already ("gitea-release-drafter").

hakre 4y ago
Nice, perhaps is worth to invest into such kind of "fediverse" (using Codeberg with my own hosted action runners/boxes), I'd buy into that feature much faster than into any other (e.g. using Codeberg for PRs from proprietary hosted "Codeberg" instances).
- RamblingCTO 4y ago
  There's also work on that ;) the dude doing most of the work moved to forgejo and some parts are already implemented but I'm not sure what the state is. I would also love to see federation, that's what would really be a github killer and drive this ecosystem forward imho. - https://github.com/go-gitea/gitea/issues/18240 https://github.com/go-gitea/gitea/issues/18240 - https://codeberg.org/forgejo/forgejo/issues/59 https://codeberg.org/forgejo/forgejo/issues/59
kotatsuyaki 4y ago
Glad to see new options. I wonder if Codeberg is going to enable actions, given that they’ve already setup an experimental instance of Woodpecker that can be requested [1] on a per-user basis. [1]: https://codeberg.org/Codeberg-CI/request-access https://codeberg.org/Codeberg-CI/request-access

xvilka 4y ago

SourceHut[1] has CI out of the box[2]. [1] https://sourcehut.org https://sourcehut.org [2] https://man.sr.ht/tutorials/getting-started-with-builds.md https://man.sr.ht/tutorials/getting-started-with-builds.md