It appeals to me as someone who likes Circle's CI offering but wants to move away from Github.
I tried using Gitlab's CI and was surprised at how limited it was. The Gitlab CI syntax was harder to follow, and my integration tests took 17m to run when they ran in almost 1/3 the time on Circle.
A big part of the problem was that CircleCI lets me use an instance with 8 CPUs / 16 GB RAM with just a config file change[0], whereas every Gitlab instance is 1 CPU / 3.75 GB RAM unless you host your own runners.[1] But if I'm paying a company to manage CI, I don't want to provision my own hardware infrastructure
Related, GitHub has had 'use more powerful hosted runners' in the pipeline for over 2 years[0]. This issue replaced another now-deleted issue[1] from July 2020.
Really disappointing, as I've had to resort to using `az vm start` -> run -> `az vm deallocate` to use an on-demand powerful runner.
I imagine non-core-product teams at Google are encouraged to submit purchase requests for any tools they think would improve their processes instead of being constrained to existing solutions. They also could just be showing it because someone with an @google.com has a paid account, but I don't know for sure :)
I would think that it also brings the advantage of having tried the actual product in their own ecosystem, Google have a good overall insight into it in case they want to buy it - not sure if this is actually the case though.
Great market fit, runners are the worst part of GitHub Actions so I'm really glad to see a product enter this space as a drop-in replacement. Will definitely check this out for my pipelines.
As a former CircleCI customer (my new employer uses Gitlab) I can highly recommend them. They make that issue so easy. You can even request GPU machines and it all works really well.
I tried using Gitlab's CI and was surprised at how limited it was. The Gitlab CI syntax was harder to follow, and my integration tests took 17m to run when they ran in almost 1/3 the time on Circle.
A big part of the problem was that CircleCI lets me use an instance with 8 CPUs / 16 GB RAM with just a config file change[0], whereas every Gitlab instance is 1 CPU / 3.75 GB RAM unless you host your own runners.[1] But if I'm paying a company to manage CI, I don't want to provision my own hardware infrastructure
[0] https://circleci.com/docs/configuration-reference#docker-exe...
[1] https://docs.gitlab.com/ee/ci/runners/saas/linux_saas_runner...