control history tagging per project #4794
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change introduces the
tagsEnabledper project/repository tunable that allows to control whether tags should be applied to history entries (so that they are visible in history view).This will require a change to https://github.com/oracle/opengrok/wiki/Per-project-configuration
Tested with the indexer running with:
and the
/var/opengrok/etc/ro-config-project.xmloverriding thetagsEnabled:Then after the indexing is done, check that the history view contains list of tags.
The indexer log entry relevant to the repository: