8 ms·
I think the majority of developers & companies doesn't want one product that does everything. It's better for the user to have clear APIs, solve specific proble
by moritzplassnig 9y ago
I think the majority of developers & companies doesn't want one product that does everything. It's better for the user to have clear APIs, solve specific problems very well and then make it easier to integrate with other products. It should all be building blocks that work well together. You should be able to use, e.g., GitHub because you prefer it over Bitbucket, integrate it with Codeship (or whatever other CI/CD solution you like) and then add other products like Percy or Code Climate as needed. There's a use case, and some people prefer to get everything out of one hand, but if we look at how software is getting purchased nowadays, it's more and more team-focused, fewer company-wide purchases. That's great. Pick the tools and products that solve your specific problem very well, as long as they integrate well with what the rest of your team uses.
Now that doesn't mean you couldn't build a company that does everything, or that Microsoft couldn't start acquiring and then does everything (they kind of doing it already, same with AWS). What we can see, though, is that the quality of specific products isn't that great. That's not surprising. It's easier to do a few things very well vs. 200 things.
And yes, I'm biased because of Codeship :)
- mschuster91 9y ago> It's better for the user to have clear APIs, solve specific problems very well and then make it easier to integrate with other products. At my company, some teams use the integrated GitLab CI features and other teams use a linked Jenkins instance, and both work well with Sonar. The only thing that is not linked automatically to this (or, at least, not in the best possible way) is the Atlassian stack because the integration plugins needed cost a boatload of money.
- sytse 9y agoWe're trying to do complete DevOps with GitLab https://about.gitlab.com/2017/10/11/from-dev-to-devops/ https://about.gitlab.com/2017/10/11/from-dev-to-devops/ What part of the Atlassian stack are you missing in GitLab?
- mschuster91 9y ago> What part of the Atlassian stack are you missing in GitLab? Well, customers and our employees are used to JIRA and Confluence. What I am talking about is proper automated linking of Gitlab branches/MRs/commits to (multiple) JIRA tickets and Confluence pages and vice versa. Basic interfacing is working but it could be done better if we'd shell out thousands of dollars per year.
- sytse 9y agoWe have extensive support for Jira, see https://about.gitlab.com/features/jira/ https://about.gitlab.com/features/jira/ for an overview and please let m Us know if you miss anything.