Skip to end of banner
Go to start of banner

Administration

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Smarter Search for Bitbucket has advanced configuration settings. These settings should only be adjusted by advanced users.


SettingDescription
Internal ES NodeCheck this box to use an internal elasticsearch service.
IndexingCheck this box to enable indexing of new source code & commits
Indexing Concurrency LimitMaximum number of concurrent indexing jobs
Max FilesizeMaximum size (in bytes) of source code files to index
Search TimeoutTimeout (in ms) of all search requests
Unhighlighted ExtensionsComma-separated list of file extensions to exclude from syntax highlighting
Preview LimitMaximum number of lines to display for file previews
Match LimitMaximum number of lines to display for file matches
Fragment LimitMaximum number of match fragments to display for file matches
Page SizeNumber of results to display per page
Commit Hash BoostBoosting factor of results with matching commit hashes (relative to source code matches)
Commit Subject BoostBoosting factor of results with matching commit subjects
Commit Body BoostBoosting factor of results with matching commit message bodies
Filename BoostBoosting factor of results with matching file names

Repository Settings

By default, only master and develop are indexed. Individual repo admins may modify these settings as follows:

  • Go to the Smarter Search for Bitbucket Repository Settings page in your repository settings panel.
  • Change the ref regex to match your desired branches.
  • Click Save or Save and Reindex to save the settings and subsequently reindex all repositories.

For example if we wanted to add the branch my-branch, we would modify the regex to look like :

HEAD|(refs/heads/(master|develop|my-branch))

You can also disable indexing for a specific repository.

Plugin Logging

Early plugin versions use several files for logging

The following log files were placed to <bitbucket-home>/home/logs/ folder:

Log fileType of logs
sfb-plugin.logAll logs of nominal plugin operations, with any errors.
sfb-plugin-debug.logAll logs of nominal plugin operations, as well as debugging logs.
sfb-elasticsearch.logLogs for only the internal Elasticsearch node.
sfb-elasticsearch-debug.logLogs for only the internal Elasticsearch node, as well as debugging logs.

As of version 2.9 logging system is changed to use atlassian-bitbucket.log for everything. Amount of information logged is controlled by logging level

To enable debug logging execute the following command:

curl -u admin:<password> -v -X PUT -H "Content-Type: application/json" <bitbucket url>/rest/api/latest/logs/logger/com.mohamicorp.stash.searchforstash/debug

To disable the debug output, restart your Bitbucket or run the following command:

curl -u admin:<password> -v -X PUT -H "Content-Type: application/json" <bitbucket url>/rest/api/latest/logs/logger/com.mohamicorp.stash.searchforstash/info
  • No labels