Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 23,561
    • Issues 23,561
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 820
    • Merge Requests 820
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #12147

Closed
Open
Opened Jun 13, 2019 by DJ Mountney@twk3
  • Report abuse
  • New issue
Report abuse New issue

Add repository code indexing for tags to elasticsearch

Problem to solve

When searching code based on a string, such as the output from an error message, if the string does not appear in the default branch, it will not return in search results.

We've determined that indexing all branches isn't overly useful, and takes up a lot of space. But tags indicate a significant code milestone, and are often widely communicated as the release version of a product. Being able to search within a tag is useful, and might be more reasonable than branches from a storage requirement standpoint.

Intended users

Developer

Further details

Often you can run into this with libraries you depend on. You are dependant on a specific tagged version of the code, not on the master branch. And you want to investigate what is sending the error message, to better understand it. If the error message has been changed or removed in master, you still want to be able to find it in a specific tag.

Proposal

  • Add tag indexing in addition to indexing the default branch

  • Most likely include an option to turn it off for projects that overuse tags or

    • Consider a max tags option, index only the 20 closest tags to master in commits?
  • Some way of showing which tag the match was found in, and likely filtering the search by tag. (Maybe default filter is for master)

Related issues

  • Discussion
  • Designs
Assignee
Assign to
Awaiting further demand
Milestone
Awaiting further demand
Assign milestone
Time tracking
None
Due date
None
8
Labels
Accepting merge requests Category:Search Create [DEPRECATED] Enterprise Edition devops::enablement elasticsearch feature group::search
Assign labels
  • View project labels
Reference: gitlab-org/gitlab#12147