|
|
|
|
|
|
by sytse
2613 days ago
|
|
|
There are many products that integrate with GitLab, see https://about.gitlab.com/partners/ There are not as many as GitHub since more is part of GitLab itself. But we're open to supporting anything, even if it competes with GitLab functionality. Regarding the example you gave for wanting Code Climate. GitLab has similar functionality as a part of the product, it is called code quality and is based on Code Climate engines, see https://docs.gitlab.com/ee/user/project/merge_requests/code_... for more information. |
|
|
I don't think it's fair to say that GitHub has more simply because it has less built-in functionality as compared to GitLab.
I agree that GitLab has broader functionality than GitHub, but it isn't so broad as to cover the breadth of functionality provided by all of GitHub's integrations combined.
Code Climate is a good example - yes you're right you have builtin quality reports, but setting it up is significantly more complex than on GitHub, and as an example serves to illustrate what I see as the very different attitudes and approaches towards building an eco-system.
Referring to your docs on code quality[1], you need to edit the CI configuration file, understand what a docker-in-docker executor is on runners etc.
Compare this to GitHub's Code Climate integration[2]: single button "Set up a plan" that guides you through s small number of screens and links your account and presto done.
Things that successful marketplaces like Heroku, GitHub, Atlassian, Slack etc get right are the ease with which to add integrations and the seamlessness of the experience.
Single button provisioning, combined billing, single sign-on etc. Just the way GitLab position the idea of integrations makes it seem to me that creating a platform isn't a priority for you (which is totally fine obviously, you're focusing on your priorities, and clearly doing pretty damn well doing so).
GitHub makes their marketplace and integrations front and centre, have extensive developer guides, etc. GitLab's are a bit more... spartan. They're lacking any real spark, they're not inviting. Compare your overview[3] page to the best equivalent I think I could find on GitHub[4]. They're chalk and cheese.
Again this isn't to say GitLab's approach is wrong, its just a different focus.
More specific feedback (and this may have changed since we evaluated it a year ago) a GitLab integration could only perform API actions as a real user of a GitLab account. We wanted to build an integration that would add comments to merge requests, but not be attributed to a real user, but a bot user for the integration. That wasn't (or at least wasn't easily discoverable) possible back then, and was a show stopper for our integration.
1: https://docs.gitlab.com/ee/ci/examples/code_quality.html 2: https://github.com/marketplace/code-climate 3: https://about.gitlab.com/partners/integrate/ 4: https://developer.github.com/