4 ms·
Makes for a tough pitch at an established shop with existing tools already in place.
by mikepurvis 10y ago
Makes for a tough pitch at an established shop with existing tools already in place.
- sytse 10y agoWe want to play nice with established tools and give people the option to use them. We have: 1. Extensive JIRA integration (and we're working on improving this) https://docs.gitlab.com/ee/project_services/jira.html https://docs.gitlab.com/ee/project_services/jira.html 2. Jenkins support https://docs.gitlab.com/ee/integration/jenkins.html https://docs.gitlab.com/ee/integration/jenkins.html via our commit status API https://docs.gitlab.com/ee/api/commits.html https://docs.gitlab.com/ee/api/commits.html 3. Slack integration https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/project_services/slack.md https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/proj... and we're working on a Slack bot https://gitlab.com/gitlab-org/gitlab-ce/issues/20799 https://gitlab.com/gitlab-org/gitlab-ce/issues/20799 We realize that we should allow other tools to integrate well and want to open up as much as we can via API's.
- theunquietone 10y agoWe hope to create tools and resources to make that pitch and migration easier. Out of curiosity, what tools are you currently using? We think it'll be a piece by piece migration versus all at once. In a perfect world, we have a tool for an all at once migration but perhaps that will come with time.
- mbreese 10y agoThe problem with that approach is that you're limited by the quality of your weakest tool. Code review might be a strength, but if your CI tool is weak, that's what you'll be judged on. Integrations are a way to allow you to focus on what you do best and effectively outsource the rest. Ideally, the integration hooks would be well integrated, but I don't see an upside in trying to make a monolithic app in this market.
- jobvandervoort 10y agoGitLab allows you to integrate with your existing tools if you please or require. But if you're fine using our tools (which are awesome, if you'd ask me), setup and cost will be zero.
- cryptos 10y agoI agree. It is essentially the same vision like the old ALM tools had. They were beaten by better more specialized tools following the unix philosophy: do one thing and do it well.
- Roritharr 10y agoWe've just opted for GitLab EE, the True-Up Licensing Model won us over, but also the promise of a working Jira Integration. That's still very limited and a pita to setup, even harder when you use atlassians hosted Jira. I don't want to buy GitLab Licenses for non-developers, especially as our Jira is connected to Zendesk, something which doesn't make sense to connect directly to GitLab.
- sytse 10y agoWe already have an extensive JIRA integration https://docs.gitlab.com/ee/project_services/jira.html https://docs.gitlab.com/ee/project_services/jira.html But I agree we can do better. If something is unclear please email support@ our company domain to get help. But I agree with your comment that we should extend the scope of the integration and make it work better with hosted JIRA. Our VP of Engineering is assigning someone to this task. Feel free to email stan@ company domain with a link to this comment and with what you need so we can have an engineer look into it. Many companies use JIRA and it should work great with GitLab.
- mikepurvis 10y agoApart from GitLab, we're mostly on Atlassian, and pretty strongly committed to JIRA and Confluence. The CI solution in GitLab is inadequate for our needs; we require the flexibility and extensibility of Jenkins. The review tool in GitLab has some significant gaps compared with standalone tools like ReviewBoard, and even compared with the one built into Bitbucket. It also has some baffling UX decisions, like the thumb/emoji buttons and the approve/merge buttons which appear in the exact same location as each other. Seriously, just scrap what you have and copy Bitbucket's review interface.
- mordocai 10y agoI'm not a gitlab employee or anything, but I'm curious: How is gitlab CI not flexible enough for you? I mean, it basically just runs arbitrary docker containers. From my mostly amateur (when it comes to this, i'm a professional developer but I don't manage our CI system directly) point of view it seems like the gitlab CI is more flexible than jenkins not less.
- sytse 10y agoAs you indicated we hope that GitLab CI covers all use cases but we're always interested in learning things we can improve.
- elygre 10y agoI added a comment to the parent, regarding test reporting. It's a showstopper for us.
- mikepurvis 10y agoThe strong coupling between repos and CI jobs is a huge obstacle— for a multi-repo codebase, you need to have triggers that are outside of "a new commit has been pushed". The reporting is a big problem too— Jenkins has plugins which format and report on JUnit-style reports, including displaying images or other assets generated by tests. Configuration. The config needing to be committed to the repo is an issue. For many use cases including ours, it's way better to have the CI configuration stored centrally somewhere, and deployed using Jenkins Job Builder (or the various other similar tools which exist for Jenkins). Executor control. Jenkins lets you do things like put N slots on a buildslave and then have a job occupy M of them, as well as controlling what jobs can run where, and what the priority of different jobs is. This is critical for ensuring overall sanity and efficiency in the pipeline. Jenkins isn't perfect, but it happens to be a better fit for our needs, and these four factors are all a big part of that.
- omnibrain 10y agoBut it's a great pitch for a shop with limited ressources that currently has nothing.
- Grangar 10y agoWe're currently moving to the Atlassian stack, from Bitbucket to Jira to Confluence. I really want to switch over to Gitlab reading this but the sunk cost is too huge already...
- sytse 10y agoWe want to play nice with existing tools. For example we're spending a lot of time improving our JIRA integration https://docs.gitlab.com/ee/project_services/jira.html https://docs.gitlab.com/ee/project_services/jira.html Most of our new users use only part of GitLab's functionality and we want to support that use case with extensive integrations and APIs.
- harbottle 10y agoHey Sid, have you seen this: https://github.com/dka23/gitlab-github-proxy https://github.com/dka23/gitlab-github-proxy. I packaged it up and I already use it successfully with GitLab EE on-site: https://gitlab.com/harbottle/glghproxy-packager https://gitlab.com/harbottle/glghproxy-packager The approach of including a GitHub -> GitLab API translation layer would allow GitLab to integrate with any application that can use GitHub. I've added this info to this ticket: https://gitlab.com/gitlab-org/gitlab-ce/issues/20418#note_15372111 https://gitlab.com/gitlab-org/gitlab-ce/issues/20418#note_15... Big fan of GitLab btw, keep up the good work!