hey nerds! i got a lovely email from GitHub this morning that their increasingly vibe-coded, barely-working Actions features are about to get more expensive (charging by the minute for something that notoriously spin-locks is a special flavor of shit sandwich).

i usually just use whatever i’m given at wherever i’m working. i do have a project that i maintain to parse Ollama Modelfiles tho: https://github.com/covercash2/modelfile and to be honest, Actions is the only solution i’ve ever used that came close to sparking joy, simply because it was easy to use and had tons of community mind-share (i’ve definitely heard horror stories and would never stake my business on it), but this price increase and all the other news around GitHub lately has got me side-eying self-hosting solutions for my git projects. Forgejo seems like the way to go for git hosting, but Actions in particular Just Works™️ for me, so i’m kind of dreading setting something up that will be yet another time sink/rabbit hole (just in time for the holidays! 🙃).

i can install most of my tooling with my language toolchain (read: rustup and cargo) which makes things fairly neat, but i just don’t have a sense for what people use outside of Jenkins and Actions.

i thought this community might have some insight beyond the LLM generated listicles that have blighted modern search results.

thanks in advance 🙏

  • TheHolm@aussie.zoneEnglish
    0·
    6 days ago

    Woodpecker. No BS CI which can be attached to pretty much anything. It just need a webhook and way to pull your project.

  • killabeezio@lemmy.zipEnglish
    0·
    9 days ago

    So many these days. Actions are probably one of the best, but there are still plenty of others out there.

    • gitlab
    • dagger
    • concourseci
    • tekton
    • Spinnaker
    • harness
    • argo
    • flux
    • gocd

    If I were to pick one, it would probably be dagger. Or really anything but Jenkins.

  • Carol2852@discuss.tchncs.deEnglish
    0·
    9 days ago

    I’m using gitea which has CI compatible to GitHub actions with my own runner. It’s pretty straightforward to set up and didn’t give me any headaches yet. It’s a very small instance just for my ownaybe dozen projects though.

    • chrash0@lemmy.worldOPEnglish
      0·
      9 days ago

      good lead. it’s just the one project for now, and to my surprise it’s actually a dependency for the ollama-rs project, so i feel somewhat obligated to keep it stable.

      • chocrates@piefed.worldEnglish
        0·
        9 days ago

        I get the hate but did you ever have to maintain jenkins pipelines? I’ll take yaml any day.

        I’m game to explore the next evolution though.

    • yaroto98@lemmy.worldEnglish
      0·
      9 days ago

      This is what I was using till I switched to forgejo and never got around to setting up one of their runners.

      • Carol2852@discuss.tchncs.deEnglish
        0·
        9 days ago

        I run their act binary on one of my servers. Can’t remember much of the setup, so I can’t be too bad. I did have to change the used images though, but I guess that comes with maintenance of you own runner anyway.

      • cecilkorik@lemmy.caEnglish
        0·
        9 days ago

        If it helps motivate you to give it a shot, I found gitea’s runner very confusing to set up, but I felt like forgejo was better designed, pretty easy and well documented.

      • Finn@toot.fan
        0·
        9 days ago

        @yaroto98 @Carol2852 Same here, switched from gitea to forgejo. I still was using the act runner for some time, later I replaced it with the forgejo-runner.

        Works pretty smooth!

      • witten@lemmy.worldEnglish
        0·
        9 days ago

        Out of curiosity, how did you switch to Forgejo? I thought Gitea and Forgejo have diverged to the point where you can no longer just switch over without losing stuff.

        • yaroto98@lemmy.worldEnglish
          0·
          8 days ago

          I hadn’t used gitea for long. I just had both running, and then cloned my repos one at a time manually. So long as I had the code, I didn’t really care.

  • fruitycoder@sh.itjust.worksEnglish
    0·
    9 days ago

    Git lab CI is my goto for git repo based things (unit tests, integration tests, etc). Fleet through Rancher for real deployments (manages and maintains state because kubernetes). Tekton is my in between catchall.

  • douglasg14b@lemmy.worldEnglish
    0·
    9 days ago

    GitHub Actions mostly.

    The rest is usually plumbing and code to support it. The actions are just the automated execution environment.

  • verstra@programming.devEnglish
    0·
    9 days ago

    I’m currently looking into Concourse.

    It does have steeper-than-average learning curve, but I really like that it has well-defined fundamentals (resources, jobs, tasks) and isolation with OCI containers. Before I adopt it fully, I want it to run my nix flake dev shell.

  • elephantium@lemmy.worldEnglish
    0·
    9 days ago

    We use Azure Devops at my current gig. It works pretty well for our setup. I’ve used GHA before; it definitely didn’t “spark joy”. I wastedspent way too many hours in the “update yaml file, commit, push, wait 5 minutes for it to fail again” spiral of despairfeedback loop.

    Nice thing with ADO is its release dashboard – you get a really nice summary of recent builds and where they went:

    $project - dev - test - prod

    I didn’t see anything similar for GHA.

    • douglasg14b@lemmy.worldEnglish
      0·
      9 days ago

      A lot of that pain can be reduced by writing and running your code locally before pushing it to a CI environment. Generally with our automation we write a CLI, And GitHub actions is just an execution environment that calls the CLI.

      And if what you’re trying to do must execute inside an action. You can run workflows locally with docker!

  • weastie@lemmy.worldEnglish
    0·
    9 days ago

    I do devops at work and my experience is that really any CI/CD system works, they all have enough features to do what you want. They all fundamentally just run scripts on boxes. Therefore, I say pick the easiest one, likely the one that is built into whatever Git system you are using.

    Try to keep your pipelines simple-ish when you can, they almost never need to be that complicated. 95% of the time it’s just running a command or two. If a pipeline needs to do something complex, I’d recommend writing that script into the Git repo and calling it, rather than having a CI job that is 100 lines long.

  • thesmokingman@programming.devEnglish
    0·
    9 days ago

    Please don’t take me as a GH shill because I’m not. I’m not sure we read the same email given your projects. Actions on GH runners are dropping in cost and there’s a new fractional cost for self-hosted. For the average user, especially those on GH runners, costs are going down. Looking at your repo, you haven’t run anything since July. Your workflow files use GH runners. Nothing in your history suggests you’re leaving the free tier so I don’t get this FUD at all. General Microsoft hate? Fuck yeah. Shitty GH service? Fuck yeah. Plenty of reasons to dunk but this was not one of them. M