If the other commenters are correct that the new CEO has a track record of pursuing private equity type acquisitions, then I fear GitLab CI is destined to become the next Travis CI.
* Bad error handling. Ruby errors leak through. Although the underlying error is my user error, returning it to me as an underlying Ruby exception is really unhelpful. It basically shows that they didn't validate inputs at all. The input is trusted, so it's probably not a security issue, but it's a huge usability and developer experience issue.
* Config format is weird and deficient. Surprisingly difficult to programmatically generate. Can't generate new jobs into the current pipeline. Must generate child pipelines. See above for the load amplification issue therein.
GitHub actions still aren’t k8s native, you actually have to install docker on your “runners” like it’s the year 2010. Pitiful.
I get the point about it not being ideal for self-hosted runners, not having ephemeral storage etc. But I disagree that the hosted GitHub Actions runners don't provide a good experience. If your build needs it - e.g. you're building something to deploy to your K8s cluster, use your Dockerfile and build in Docker. If you just want to compile some code, what's the point?