3 ms·

Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separ

Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system.

KronisLV 4y ago
> Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system. I'm in the opposite camp, especially when this separate system is as simple as Drone CI or Woodpecker CI (I mostly use the former, but the latter is more permissive, license wise). I came to holding this view after I ran into some issues by using a self-hosted GitLab Omnibus install previously: https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-nexus-and-drone https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-... Using separate systems for working with the code, doing CI/CD and storing artifacts made each of the parts easier to update, limit the resources available to each, as well as limited the fallout when something does go wrong - say, still being able to interact with the codebase, even if the container repo is temporarily unavailable, or vice versa. That said, in a few years I might come around to holding the opposite views again - frankly, both approaches are good and seeing the Gitea Actions project is nice! Though I'll also acknowledge that some might claim that all-in-one solutions are sometimes a bit half-baked, a criticism that I've heard of GitLab in the past (though honestly they're also fine, especially for the more enterprise settings, where you have beefier servers and a few people to manage the install).
- fjni 4y ago
  I'm with you on this. I would expand this further yet and say that introducing this as a feature creates a whole set of security concerns that just weren't there before.
- potamic 4y ago
  Concur. Composability, separation of concerns, do one thing and one thing well, etc. are all philosophies as old as time in this industry. Any programmer worth their salt would understand the value they provide. Source code hosting has nothing to do with building your software and it's a bad idea to mix them up. This situation is actually a bit more insidious. All these CI/CD features are just a thinly veiled attempt at locking users into the platform. There's not big money to be made selling git hosting, but if you control how the software is built, then you have made yourself a hard dependency. If you look at the starter workflows they provide, they encourage bad practices where your application build is defined in their DSL. Experienced programmers might steer away from such usage, but many novice won't. If you have enough novice adoption, it becomes the norm. So many projects these days cannot even be built locally without a CI service dependency, where instead 99% of the time, all you needed was a simple makefile.
jamesu 4y ago
Gitea actions looks neat though I'm not sure how you are meant to run windows or mac-centric workflows with it since the runtime (nektos/act) seems to require docker. If its not possible that might limit its usefulness somewhat...
- aorth 4y ago
  > docker Alternatively, I was wondering if it supported podman. I prefer podman in most cases since it runs without root and doesn't mess with my host's nftables. Docker always invokes iptables and adds a bunch of chains/rules. Grrr...
- techknowlogick 4y ago
  One contributor to nektos/act and Gitea's act_runner (ChristopherHX) contributor "host" mode to act, which allows you to run without docker. Disclaimer: I am a part of the Gitea project, the TOC, and am employed to work on Gitea
  - candiddevmike 4y ago
    I think this is the PR: https://github.com/nektos/act/pull/1293 https://github.com/nektos/act/pull/1293 This is perfect for my needs. Thank you to the Gitea folks for getting this added/integrated!
hdjjhhvvhga 4y ago
Don't do it yet otherwise you will fill disappointed by teething problems. Do it in 3 months and then - if they keep the current dynamics - you will be able to work with GA more comfortably and only encounter minor bugs.
geek_at 4y ago
It's mindblowing for me how many of the features I love from github are now in gitea. Actions, email replies, scoped lables, fine-tunable access tokens, secrets and also the ability to push local git repos to gitea without having to create them via the web interface first.

Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system.

KronisLV 4y ago

> Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system. I'm in the opposite camp, especially when this separate system is as simple as Drone CI or Woodpecker CI (I mostly use the former, but the latter is more permissive, license wise). I came to holding this view after I ran into some issues by using a self-hosted GitLab Omnibus install previously: https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-nexus-and-drone https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-... Using separate systems for working with the code, doing CI/CD and storing artifacts made each of the parts easier to update, limit the resources available to each, as well as limited the fallout when something does go wrong - say, still being able to interact with the codebase, even if the container repo is temporarily unavailable, or vice versa. That said, in a few years I might come around to holding the opposite views again - frankly, both approaches are good and seeing the Gitea Actions project is nice! Though I'll also acknowledge that some might claim that all-in-one solutions are sometimes a bit half-baked, a criticism that I've heard of GitLab in the past (though honestly they're also fine, especially for the more enterprise settings, where you have beefier servers and a few people to manage the install).

fjni 4y ago
I'm with you on this. I would expand this further yet and say that introducing this as a feature creates a whole set of security concerns that just weren't there before.
potamic 4y ago
Concur. Composability, separation of concerns, do one thing and one thing well, etc. are all philosophies as old as time in this industry. Any programmer worth their salt would understand the value they provide. Source code hosting has nothing to do with building your software and it's a bad idea to mix them up. This situation is actually a bit more insidious. All these CI/CD features are just a thinly veiled attempt at locking users into the platform. There's not big money to be made selling git hosting, but if you control how the software is built, then you have made yourself a hard dependency. If you look at the starter workflows they provide, they encourage bad practices where your application build is defined in their DSL. Experienced programmers might steer away from such usage, but many novice won't. If you have enough novice adoption, it becomes the norm. So many projects these days cannot even be built locally without a CI service dependency, where instead 99% of the time, all you needed was a simple makefile.

jamesu 4y ago

Gitea actions looks neat though I'm not sure how you are meant to run windows or mac-centric workflows with it since the runtime (nektos/act) seems to require docker. If its not possible that might limit its usefulness somewhat...

aorth 4y ago
> docker Alternatively, I was wondering if it supported podman. I prefer podman in most cases since it runs without root and doesn't mess with my host's nftables. Docker always invokes iptables and adds a bunch of chains/rules. Grrr...
techknowlogick 4y ago
One contributor to nektos/act and Gitea's act_runner (ChristopherHX) contributor "host" mode to act, which allows you to run without docker. Disclaimer: I am a part of the Gitea project, the TOC, and am employed to work on Gitea
- candiddevmike 4y ago
  I think this is the PR: https://github.com/nektos/act/pull/1293 https://github.com/nektos/act/pull/1293 This is perfect for my needs. Thank you to the Gitea folks for getting this added/integrated!

hdjjhhvvhga 4y ago

Don't do it yet otherwise you will fill disappointed by teething problems. Do it in 3 months and then - if they keep the current dynamics - you will be able to work with GA more comfortably and only encounter minor bugs.

geek_at 4y ago

It's mindblowing for me how many of the features I love from github are now in gitea. Actions, email replies, scoped lables, fine-tunable access tokens, secrets and also the ability to push local git repos to gitea without having to create them via the web interface first.