3 ms·
We just switched from GitLab to GitHub because the CI is horrible and they changed the pricing to a very bad option in our case. Without adding features we use
by RamblingCTO 5y ago
We just switched from GitLab to GitHub because the CI is horrible and they changed the pricing to a very bad option in our case. Without adding features we use we would've had to pay four times the money.
The CI just sucks, it's very flaky and just outright unstable sometimes. The configuration is pure horror. It takes ages to implement simple stuff. In two years I didn't get sonarcloud annotations on our damn pull requests to work. The UI just sucks. I don't know why you want to switch from GitHub to GitLab? We're happy with the switch.
- dijit 5y agoThis is so contra to my own experiences that I'm wondering if your gitlab setup was horribly configured..? Did you self-host? How did you deploy it? Gitlab CI has been "the best"(tm) self-hosted CI solution I've used.
- dnsmichi 5y agoHi, we added CI workshops into the docs in the past year: https://docs.gitlab.com/ee/ci/quick_start/ https://docs.gitlab.com/ee/ci/quick_start/ and worked on more learning resources at https://about.gitlab.com/learn/ https://about.gitlab.com/learn/ The new CI/CD pipeline editor also improves the getting started experience, shown in a demo workshop in the GitLab 14 community meetup: https://www.youtube.com/watch?v=mSspEk8efHE https://www.youtube.com/watch?v=mSspEk8efHE Can you elaborate a bit more on the CI configuration problems you are running into? Thanks!
- smcleod 5y agoI've never really had any GitLab CI problems worth talking about and the key thing for us is how reliable it is. I've only ever used self hosted - maybe were you using their free / SaaS agents or something?