-
-
Extra suggestions:
- Add an option to only index the current/latest commit.
- Add a file filter. For example, my OneDev instance consumes all memory assigned to the container while indexing at least one specific file.
-
A code analysis setting already exists allowing include/exclude file patterns to be configured.
-
Ah, sorry, you're right.
-
@davidebeatrici I also experienced this issue recently. AI bots crawl each commit triggering indexing and this generates large index cache. I added a code index setting to optionally require logged-in user to trigger code indexing. It can be set in root projects and all child projects will inherit this setting.
I am closing this issue as it is no longer necessary with this option and code analysis pattern.
-
Previous Value Current Value Open
Closed
| Type |
Enhancement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Watchers (2)
Currently index of a repository commit will be created automatically which may accumulate a large index on disk. We should have settings to control whether or not to create index, and which index (full text, symbol etc) to create.