[doix]

That's an interesting perspective. I used to work at a large company with a massive Jenkins setup. The nice thing about Jenkins is that your unix skills translate. It basically just runs a shell script and you can do anything.

In GitHub actions, the process is super abstracted and opaque. It doesn't really match anything I've used before and knowledge of unix doesn't help top much. I can't really reason what will happen, things are the way they are because that's how GitHub actions work, rather than something I can work out.

I can see a certain part of the build is slow, I know how I'd fix it if I were on Jenkins land, but here it's just too abstracted. I end up just googling and finding someone else with the same problem and copying how they fixed it.

I do agree that gitlab is worse somehow than GitHub actions.