3 ms·
We had a very similar experience with Gitlab too. Our teams evaluated Gitlab for a year before completely migrating away from it (to Github Enterprise for SCM,
by waltera 7y ago
We had a very similar experience with Gitlab too.
Our teams evaluated Gitlab for a year before completely migrating away from it (to Github Enterprise for SCM, Confluence for wiki, YouTrack for issues and TeamCity for CI).
Not a single team (out of 20) was happy with the overall performance (and especially the performance of code search).
As far as wiki is concerned, Confluence's UI has its own share of issues, even after their recent overhaul, but all in all it is much better product. YouTrack and TeamCity are simply much more polished & stable products and are (in our experience) easier to administer than the competing offerings from Gitlab.
- sytse 7y agoCode search is not good at GitLab.com at the moment. We're working to enable ElasticSearch for GitLab.com to improve the situation https://about.gitlab.com/2019/03/20/enabling-global-search-elasticsearch-gitlab-com/ https://about.gitlab.com/2019/03/20/enabling-global-search-e...
- phikai 7y ago> Not a single team (out of 20) was happy with the overall performance (and especially the performance of code search). Hi! I'm the current PM for our search and as Sid mentioned we've steadily been working to improve that. It's been getting a lot better, but most of the improvements are heavily reliant on also having Elasticsearch enabled. Without that, there's really no way for us to provide a optimal search experience for the amount of data and content there. If you have any specific search feedback, please feel free to open an issue or reach out to me @phikai on GitLab.