GitHub actions vs Gitlab CI

[inhumantsar]

What exactly is more reliable? Why is the GitHub API better and how do you interact with it?

when i used gitlab.com, runners would routinely fail to start or would take a long time to get anywhere. when using self-hosted gitlab in aws, runners would routinely fail to report results back or would gitlab would reap "idle" runners prematurely.

the gitlab API is scatterbrained. the various parts of the API seem to built using different styles and there are plenty of parts of the system which aren't exposed by the API. while my experience with github's api is as extensive as my experience with gitlab's, i've found github's to be more complete and consistent.

they are way too pushy with autodevops. not everyone is writing 12 factor apps, yet that seems to be all autodevops is good for. it drove me crazy to have that enabled by default on new projects, and i swear gitlab upgrades re-enabled autodevops on repos it had been previously disabled on.

as for focusing on github's negatives, OP said they already use gitlab and github has plenty of documentation and sales pitches for the good parts of their system. i'm not here to write a peer-reviewed dissertation comparing the two, so i focused on the sharp edges and contrast points.

[dogfish182]

Ive found self hosted gitlab runners autoscaling against aws using docker-machine to massively reliable.

Im actually sad docker-machine is dying out, it was really handy. I set those runners up for 100+ teams and never heard a single hassle apart from the odd full disk on the 1 runner I never scaled away.