

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.
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.
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.
Oh…I was interested until you said actions. What a terrible system for ci.
I heard that in my bones…