3 ms·
> 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
by 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.