5 ms·
Wow, reading this and all the comments makes me realise GHA is really far behind Gitlab CI. They've at least been playing catch-up since the MS acquisition, hav
by sofixa 5y ago
Wow, reading this and all the comments makes me realise GHA is really far behind Gitlab CI. They've at least been playing catch-up since the MS acquisition, having stagnated for years before that.
I really wonder why would anyone self-host GitHub. Gitlab has a much more feature rich, mature and cheap ( there's a perfectly usable free version) offering. Yeah, someone might prefer Github's UX, but is it really worth it to pay for a worse product?
- easton 5y agoGitHub’s UX is worth it, IMO. GitLab tries to do too many things and it’s really hard to get my bearings (it’s like Azure DevOps’ problem times 10). And if GitHub Actions doesn’t work, it’s really easy to integrate third party CI solutions.
- sofixa 5y ago> GitHub’s UX is worth it, IMO. GitLab tries to do too many things and it’s really hard to get my bearings (it’s like Azure DevOps’ problem times 10). That's subjective. Gitlab does many more things, but nobody is forcing you to use them, and unused menu buttons don't matter much for the main workflows ( commits, MRs, repo visualisation, wikis, CI/CD).
- adwww 5y agoYeah I liked Gitlab when we used it for everything, but once we started to integrate with other services (Jira etc) instead of the built in functionality it felt like you were fighting how they had designed it.
- john_cogs 5y agoGitLab team member here. We've put a lot of effort into our integration with Jira. The docs [1] detail how it works and we have a blog [2] with some screenshots so you can see what it looks like in action. What kind of troubles have you encountered? 1 - https://docs.gitlab.com/ee/integration/jira/ https://docs.gitlab.com/ee/integration/jira/ 2 - https://about.gitlab.com/blog/2021/03/25/integrating-gitlab-com-with-atlassian-jira-cloud/ https://about.gitlab.com/blog/2021/03/25/integrating-gitlab-...
- adwww 5y agoThat blog is from 2021 - this was a couple of years ago so things may have changed. But back then you'd still find quite a few paths back to the Gitlab issues - it never really went away, it just replaced a few issue links.
- shoo 5y ago> I really wonder why would anyone self-host GitHub. Gitlab has a much more feature rich, mature and cheap offering. before i understood your comment i was going to reply "security, data security & control" -- as a reason orgs might choose to self-host vs outsource hosting SaaS github. But you're probably arguing for self-hosted gitlab over self-hosted github. Good question! i've worked somewhere with self-hosted github, but they were using it prior to github actions / workflows, so it was a combination of self-hosted github and N different CI and deployment automation tools ( bamboo! GoCD! udeploy! jenkins! google cloud build! poor bloody operator manually copying deployment payload onto jump box as the bureaucracy won't approve automation!)
- _jal 5y agoThat's usually the wrong question, as people only make greenfield decisions once. If, however, you've been running GHE for years and have it integrated with other tooling and workflows, and your developers understand it, the question is, "Why would anyone rip all that out, replace it, reintegrate it and retrain everyone over a handful of features, most of which you don't care about?"
- stavros 5y ago"Because there's one feature we really care about". That's why we migrated to GitLab CI. We made some pretty complicated pipelines, with tens of stages, many of them dynamic, and it worked with minimal hassle. It was a great success story internally.
- sofixa 5y ago> "Why would anyone rip all that out, replace it, reintegrate it and retrain everyone over a handful of features, most of which you don't care about Functioning CI/CD for free is certainly a huge feature to care about. For a user moving between Github and Gitlab is at worst a slight annoyance, the UX and DX are pretty similar; most third-party tooling that isn't github.com ( SaaS) only supports both Github and Gitlab self-hosted (i'd even wager there are more tools that support self-hosted Gitlab than Github, the first is much more popular).
- roblabla 5y agoHoly shit wat? Gitlab CI is a clusterfuck that is impossible to use for all but the most simple use-cases. We have a monorepo at work, and GitLab CI never fucking works. Here are some examples: - Fallback cache keys don't work (because it doesn't compose with cache changing cache ids). So each time someone clears the runner caches, the fallback cache stops working. - `if`/`rules` and `needs` don't work together, and cause the build to fail with a *yaml build failure*. Wat? This is even a documented failure mode now. This is a huge issue for monorepos. - gitlab-runner is full of weird behaviors, like `gitlab-runner unregister <runner-name>` fails if that runner was already deleted (through the gitlab UI), but won't remove it from the local config. But `gitlab-runner` has a separate command, gitlab-runner verify --delete, which does just that... It feels like every time I use it, I run into a bug. I've heavily used github actions in many projects of similar sizes, and have yet to come across a single bug.
- rossmohax 5y agoMonorepo case is solved by top level job dispatching based on path to a child pipeline, No need to make a mess of rules in a singe gitlab-ci.yml file. If child pipelines need common steps, they can be neatly included
- sofixa 5y agoA monorepo isn't "all but the most simple use-cases", it's usually a fairly complex usecase, and Gitlab have a myriad of ways to make monorepo CI easier - dynamic pipelines, remote triggers, includes, etc. > `if`/`rules` and `needs` don't work together, and cause the build to fail with a yaml build failure. Wat? This is even a documented failure mode now. This is a huge issue for monorepos Could you elaborate on this? I have a fairly complex pipeline which has rules and needs, and it works without any yaml errors.
- roblabla 5y ago> Could you elaborate on this? I have a fairly complex pipeline which has rules and needs, and it works without any yaml errors. Sorry, it was with `only:changes` and `needs`. Take a look at this issue[0] and this pipeline[1]. I've failed to find the failure mode in the documentation, so I suppose it may have been fixed since then - but we've developed an in-house workaround in the meantime that I'd trust a lot more than anything coming from Gitlab. -------- > A monorepo isn't "all but the most simple use-cases", it's usually a fairly complex usecase, and Gitlab have a myriad of ways to make monorepo CI easier - dynamic pipelines, remote triggers, includes, etc. And every single feature you've mentioned here has a bug when combined with something else. That's the problem with Gitlab CI: everything works in isolation, but nothing composes properly. Take includes: they don't work with anchors, so you couldn't have a generic template rules in the "main" file getting reused in the included files. This makes sense though! Anchors are a yaml feature. So gitlab added their own pseudo-anchors, called `extends`. You'd assume a smart, context-aware merge to happen, but no! Gitlab decided to go with a dumb object merge. Because the `script` step is a list of string, if both the parent and the child specify a `script`, only the child's will be used! Gitlab has a `before_script` step which can be used to workaround the issue for single levels of inheritance, but anything more complex ends up in a dead end. This feels like a feature that's been bolted on without any sort of design work. [0]: https://gitlab.com/gitlab-org/gitlab/-/issues/31310 https://gitlab.com/gitlab-org/gitlab/-/issues/31310 [1]: https://gitlab.com/ensc/test-ci-needs/-/pipelines/78713602 https://gitlab.com/ensc/test-ci-needs/-/pipelines/78713602