search

go-gitea / gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
https://gitea.com
MIT License
45.29k stars 5.51k forks source link

Search problems or request to customize search settings #30064

Open amix307 opened 8 months ago

amix307 commented 8 months ago

Description

My repositories contain code for CI/CD system builds such as Jenkins or Teamcity. Teamcity stores its code in the .teamcity directory, which can contain directories of several nesting levels, as well as xml, kotlin files. The problem is that Gitea's built-in Bleeve indexer ignores this directory and I get no search results in it. On the other hand, if I store the parameters for Maven in the .mvn directory, the search is successful.

I suspect this is something that can be controlled or is a bug that I would like to fix.

Gitea Version

1.21.7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Centos9 Stream

How are you running Gitea?

on-prem

Database

PostgreSQL

lunny commented 8 months ago

Can you give some example repositories?

amix307 commented 8 months ago

@lunny Of course, but on try.gitea.com search func is off. In what form can I give the repo example?

amix307 commented 8 months ago

@lunny for example, clone random repo with .teamcity directory from GH: https://github.com/jonnyzzz/TeamCity.Node Then push it to your Gitea instance with enabled search. Search something from .teamcity, for example "uploadedKey" from .teamcity/TeamCityNodePlugin/vcsRoots/git___github_com_jonnyzzz_TeamCity_Node_git.kt

amix307 commented 7 months ago

@lunny Hi! Will you be able to check? I want to understand how bleve works as part of gitea. File size limits are available, but here I clearly fit in and it selectively searches in directories with a dot at the beginning of the name

lunny commented 7 months ago

I confirmed this is a bug. I will do some investigation.