I prefer Gitlab CICD but there are many. Actions had a lot of potential. Then Microsoft bought GitHub and just slapped the Actions label on their CI. If you pull off the mask, it is just Azure devops.
Comment on Organic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.
sugar_in_your_tea@sh.itjust.works 4 weeks agoWhat’s wrong w/ actions? Is there something else you prefer?
I think they’re quite powerful. There are a variety of triggers, runners are fairly easy to configure (easy to scale up), and the syntax is pretty straightforward. It seems to work pretty well.
theherk@lemmy.world 4 weeks ago
neclimdul@lemmy.world 4 weeks ago
I do too. I kinda miss Jenkins but a lot of the conveniences in GitLab’s CI are really nice and it’s better for 99% of use cases.
neclimdul@lemmy.world 4 weeks ago
Every other ci in existence you just write a command. Then if it doesn’t work you run the command on your machine and fix it.
Actions are “magic” which means you have to fake the ci runner with tools and reverse engineer the action to run local debugging and if it failed you might not even fully know what was running with digging into the actions source.
GitHub provides you the tools and their “easy” until they aren’t.
It’s very Microsoft though. It feels like trying to write a Windows app and trying to get your random Net environment definition to line everything up and compile in VS then hoping the same thing happens when you deploy.
trevor@lemmy.blahaj.zone 4 weeks ago
You can just write bash scripts in your actions if you want them to be easily replicatable on your local machine, so you don’t really lose anything with that system.