| Hi, I'm planning on migrating away from stash to most likely gitlab in the next few weeks. One thing that keeps coming back among my team is where is the real search power. I followed the work your team did with EE and Elastic and was curious if you will plan to back port it into CE? all i read is that it's EE, but will it be brought to CE is the bigger question, and how does that fall into your current roadmap for upcoming releases in CE? ---- Follow up, do you plan on adding any code intelligence to your EE search, such as being done by the team at sourcegraph.com? The way I see it is like this...
github, sourcegraph & gogs all are missing the ability to categorize repositories in groups. This is a must when you have a lot of repos, thanks for including it. gogs = super fast, minimalistic but solid.
github = $$$$$$
stash/bitbucket = nickel and diming over features & $$$$
sourcegraph = not mature enough, missing code intelligence for majority of the languages we use
gitlab ce = great feature set, bad search and some performance struggles (that i see you are addressing) in the end, we are likely to go with your product, but the search in CE almost hurts my feelings to use. (me: search for "test" in all repos: 0 results. search for "test" in specific repo: 1 result. me: scratch my head) all in all, really excited to kick stash out and give my team a deeper feature set to play with. Thanks for taking the time to come here, I'm late to the party. |
The code management analytics we're planning to build are detailed in https://gitlab.com/gitlab-org/gitlab-ee/issues/112 I think this is quite different from sourcegraph
Your search in CE looks like a bug to me. It would be great if you can reproduce this on GitLab.com and open an issue for it.