Stash config properties

audit.highest.priority.to.log=HIGH

Defines the lowest priority audit events that will be logged.
Accepted values are: HIGH, MEDIUM, LOW and NONE.

Setting the value to HIGH will result in only HIGH level events being logged. NONE will cause no events to be logged. MEDIUM will only allow events with a priority of MEDIUM and HIGH to be logged.

Refer to the levels for the various events.

This does not affect events displayed in the Audit log screens for projects and repositories.

audit.details.max.length=1024

plugin.stash-audit.max.entity.rows=500

The maximum number of entries a project or repository can have in the audit tables.

This does not affect the data stored in the logs.

plugin.stash-audit.cleanup.batch.size=1000

When trimming the audit entries table this is the maximum number of rows that will be trimmed in one transaction. Reduce this size if you are having issues with long running transactions.

This does not affect the data stored in the logs.

plugin.stash-audit.cleanup.run.interval=24

How often the audit tables will be checked to see if they need to be trimmed (in hours).

This does not affect the data stored in the logs.

The fallback URL for Gravatar avatars when a user does not have an acceptable avatar configured. This may be a URL resource, or a Gravatar provided default set. 

This configuration setting is DEPRECATED. It will be removed in Stash 3.0. Use avatar.url.default instead.

Controls the max height and width for an avatar image. Even if the avatar is within the acceptable file size, if its dimensions exceed this value for height or width, it will be rejected. 

When an avatar is loaded by the server for processing, images with large dimensions may expand from as small as a few kilobytes on disk to consume a substantially larger amount of memory, depending on how well the image data was compressed. Increasing this limit can substantially increase the amount of heap used while processing avatars and may result in OutOfMemoryErrors. 

Value is in PIXELS.

Controls how large an avatar is allowed to be. Avatars larger than this are rejected and cannot be uploaded to the server, to prevent excessive disk usage. 

Value is in BYTES.

Controls how frequently temporary avatars are cleaned up. Any temporary avatars that have been uploaded are checked against their configured max age and removed from the file system if they are "too old". 

Value is in MILLISECONDS.

Controls how long a temporary avatar that has been uploaded is retained before it is automatically deleted. 

Value is in MINUTES.

avatar.url.format.http=http://www.gravatar.com/
avatar/%1$s.jpg?s=%2$d&d=%3$s

avatar.url.format.https=https://secure.gravatar.com/
avatar/%1$s.jpg?s=%2$d&d=%3$s

Controls the maximum number of threads which are used to perform indexing. The resource limits configured below are not applied to these threads, so using a high number may negatively impact server performance.

Controls how long indexing processes are allowed to execute before they are interrupted, even if they are producing output or consuming input. 

The value is in SECONDS

Controls how much space needs to be available on disk (specifically under <STASH-HOME>/caches) for caching to be enabled. This setting ensures that the cache plugin does not fill up the disk.

Value is in BYTES.

The JDBC driver class that should be used by Stash to connect to the database. The default Stash database uses the file-based HSQL database (org.hsqldb.jdbcDriver), storing its data in the <Stash home directory>. Stash currently bundles these other JDBC drivers:

• org.postgresql.Driver (more info)

• com.microsoft.sqlserver.jdbc.SQLServerDriver (more info)

• oracle.jdbc.driver.OracleDriver (more info)

Defines the number of statements to cache.

If you configure your JDBC driver to use loadbalancing or failover with the Stash server, you may need to set db.pool.cache.statements=0. Please note that Stash does not yet (as of version 2.8) support DB redundancy, and that this configuration change is not supported by Atlassian.

Defines the amount of time the system will wait when attempting to open a new connection before throwing an exception. The system may hang, during startup, for the configured number of seconds if the database is unavailable. As a result, the timeout configured here should not be generous. 

Value is in SECONDS.

Defines the maximum period of time a connection may be idle before it is closed. Generous values should be used here to prevent creating and destroying many short-lived database connections (which defeats the purpose of pooling).

Value is in MINUTES.

Defines the amount of time a connection may be idle before a test query is executed by the pool. This helps prevent connections from being closed by the database server due to inactivity. 

Value is in MINUTES.

Controls the download policy for raw content.

Possible values are: 
Insecure – Allows all file types to be viewed in the browser 
Secure – Requires all file types to be downloaded rather than viewed in the browser 
Smart – Forces "dangerous" file types to be downloaded, rather than allowing them to be viewed in the browser 
These options are case-sensitive and defined in com.atlassian.http.mime.DownloadPolicy

The time a dispatcher thread will be kept alive when the queue is empty and more than core.threads threads are running. 

Value is in SECONDS.

Controls how long idle threads are kept alive. Threads idle for more than this time will be terminated.

Value is in SECONDS and must be >= 1. If 0 or a negative value is used, a default value of 1 will be configured.

Controls whether to require CAPTCHA verification when the number of failed logins is exceeded. If enabled, any client who has exceeded the number of failed logins allowed using either the Stash web interface or the Git hosting interface will be required to authenticate in the Stash web interface and successfully submit a CAPTCHA before continuing. Setting this to false will remove this restriction and allow users to incorrectly authenticate as many times as they like without penalty.

Warning: It is STRONGLY recommended you keep this setting enabled. Disabling it will have the following ramifications:

• Your users may lock themselves out of any underlying user directory service (LDAP, Active Directory etc) because Stash will pass through all authentication requests (regardless of the number of previous failures) to the underlying directory service.
• For Stash installations where you use Stash for user management or where you use a directory service with no limit on the number of failed logins before locking out users, you will open Stash or the directory service up to brute-force password attacks.

Controls whether personal repositories can be ceated.

When set to false, personal repository creation is disabled globally in Stash

hibernate.format_sql=false 

When hibernate.show_sql is enabled, this flag controls whether Hibernate will format the output SQL to make it easier to read.

hibernate.jdbc.batch_size=20

Controls Hibernate's JDBC batching limit, which is used to make bulk processing more efficient (both for processing and for memory usage).

hibernate.show_sql=false

Used to enable Hibernate SQL logging, which may be useful in debugging database issues. This value should generally only be set by developers.

plugin.jira-integration.pullrequest.attribute.changesets.max=100

Controls the maximum number of changesets to retrieve when retrieving attributes associated with changesets of a pull-request. This value should be between 50 and 1000 as Stash will enforce an lower bound of 50 issues and an upper bound of 1000 issues.

plugin.jira-integration.remote.page.max.issues=20

Controls the maximum number of issues to request from JIRA. This value should be between 5 and 50 as Stash will enforce a lower bound of 5 issues and an upper bound of 50 issues.

plugin.jira-integration.remote.timeout.connection=5000

The connection timeout duration in milliseconds for requests to JIRA. This timeout occurs if the JIRA server does not answer. e.g. the server has been shut down. This value should be between 2000 and 60000 as Stash will enforce a lower bound of 2000ms and an upper bound of 60000ms. 

Value is in MILLISECONDS.

plugin.jira-integration.remote.timeout.socket=10000

The socket timeout duration in milliseconds for requests to JIRA. This timeout occurs if the connection to JIRA has been stalled or broken. This value should be between 2000 and 60000 as Stash will enforce a lower bound of 2000ms and an upper bound of 60000ms 

Value is in MILLISECONDS.

liquibase.commit.block.size=10000

The maximum number of changes executed against a particular Liquibase database before a commit operation is performed. Very large values may cause DBMS to use excessive amounts of memory when operating within transaction boundaries. If the value of this property is less than one, then changes will not be committed until the end of the change set.

plugin.stash-notification.mail.max.comment.size=2048

Controls the maximum allowed size of a single comment in characters (not bytes). Extra characters will be truncated.

plugin.stash-notification.mail.max.description.size=2048

Controls the maximum allowed size of a single description in characters (not bytes). Extra characters will be truncated.

plugin.stash-notification.mentions.enabled=true

Controls whether mentions are enabled

plugin.stash-notification.max.mentions=200

Controls the maximum number of allowed mentions in a single comment

page.max.branches=1000

Maximum number of branches per page.

page.max.changes=1000

Maximum number of changes per page. Unlike other page limits, this is a hard limit; subsequent pages cannot be requested when the number of changes in a changeset exceeds this size.

page.max.changesets=100

Maximum number of changesets (commits) per page.

page.max.diff.lines=10000

Maximum number of segment lines (of any type, total) which may be returned for a single diff. Unlike other page limits, this is a hard limit; subsequent pages cannot be requested when a diff exceeds this size.

page.max.directory.children=500

Maximum number of directory entries which may be returned for a given directory.

page.max.directory.recursive.children=100000

Maximum number of file entries which may be returned for a recursive listing of a directory. A relatively high number as this is used by the file finder which needs to load the tree of files upfront.

page.max.groups=1000

Maximum number of groups per page.

page.max.index.results=50

Maximum number of changesets which may be returned from the index when querying by an indexed attribute. For example, this limits the number of changesets which may be returned when looking up commits against a JIRA issue.

page.max.projects=1000

Maximum number of projects per page.

page.max.repositories=1000

Maximum number of repositories per page.

page.max.source.length=5000

Maximum length for any line returned from a given file when viewing source. This value truncates long lines. There is no mechanism for retrieving the truncated part short of downloading the entire file.

page.max.source.lines=5000

Maximum number of lines which may be returned from a given file when viewing source. This value breaks large files into multiple pages.

page.max.tags=1000

Maximum number of tags per page.

page.max.users=1000

Maximum number of users per page.

page.scan.pullrequest.activity.size=500

The size of the page Stash should use when scanning activities.

page.scan.pullrequest.activity.count=4

The number of pages of activities Stash should scan before giving up.

password.reset.validity.period=4320

Controls how long a password reset token remains valid for. Default period is 72 hours.

Value is in MINUTES.

process.timeout.execution=120 

process.timeout.idle=60

Controls timeouts for external processes, such as Git and Hg. The idle timeout configures how long the command is allowed to run without producing any output. The execution timeout configures a hard upper limit on how long the command is allowed to run even if it is producing output. 

Values are in SECONDS. Using 0, or a negative value, disables the timeout completely.

USE AT YOUR OWN RISK!

plugin.stash-scm-git.pullrequest.merge.
strategy.KEY.slug=no-ff

Control the merge strategy for a repository (where KEY is the project key and slug is the repository slug). Note that the URL for the browse page of a repository is of the following form: http://<stashdomain>/projects/<PROJECTKEY>/repos/<reposlug>/browse

Overrides project and global settings.

Possible values are:

• no-ff – no fast-forward; the default setting.

• ff – allow fast-forward; will merge when necessary.
• ff-only – require fast-forward; will never create merge commits; fail if a merge is required.
• squash – collapse all incoming commits into a single commit directly to the target branch; never create a merge.
• squash-ff-only – collapse all the incoming commits into a single commit directly to the target branch, never creating a merge, but do so only if the source branch is fast-forward.

plugin.stash-scm-git.pullrequest.merge.
strategy.KEY=no-ff

Control the merge strategy for a project (where KEY is the project key).

Overrides global settings. Is overridden by repository settings.

Possible values are listed above.

plugin.stash-scm-git.pullrequest.merge.
strategy=no-ff

Control the merge strategy globally. Is overridden by repository and project settings.

Possible values are listed above.

pullrequest.diff.context=10

Defines the number of context lines to include around diff segments in pull request diffs. By default, Git only includes 3 lines. The default is 10, to try and include a bit more useful context around changes, until the ability to "expand" the context is implemented.

pullrequest.rescope.changesets.display=5

Defines the maximum number of changesets per type (either added or removed) to display in a rescope activity.

pullrequest.rescope.changesets.max=1000

Defines the absolute maximum number of changesets that will be evaluated when attempting to determine, for a given rescope activity, which changesets were added to or removed from a pull request. Adjusting this setting can have significant memory footprint impact on the system. It is not recommended to be changed, but the option is provided here to support unique use cases.

pullrequest.rescope.detail.threads=2

Defines the maximum number of threads to use for precalculating rescope details. These threads perform the requisite processing to determine the commits added and removed when a pull request is rescoped, where most rescopes do not add or remove any commits. Such "dead" rescopes are deleted during processing. The primary goal is to ensure all details have already been calculated when users try to view a pull request's overview.

pullrequest.rescope.drift.threads=4

Defines the maximum number of threads to use when processing comment drift for a pull request during rescope. Higher numbers here do not necessarily mean higher throughput! Performing comment drift will usually force a new merge to be created, which can be very I/O intensive. Having a substantial number of merges running at the same time can significantly reduce the speed of performing comment drift.

plugin.stash-readme.max.size=65536

Controls the maximum allowed size of a readme file to parse. 

Value is in BYTES.

ref.metadata.timeout=2

Controls timeouts for retrieving metadata associated with a collection of refs from all metadata providers collectively.

This values is in SECONDS.

throttle.resource.scm-command=25

Limits the number of operations that support the UI, such as git diff, git blame, or git rev-list, that can run concurrently. This is intended to prevent these SCM commands from competing with the running of push and pull operations.

throttle.resource.scm-command.timeout=2

Controls how long threads will wait for SCM commands to complete when the system is already running the maximum number of SCM commands.

Value is in SECONDS.

throttle.resource.scm-hosting=1.5*cpu

Limits the number of SCM 'hosting' operations, such as git clone, git push and git pull over HTTP or SSH that may be running concurrently. This is intended primarily to prevent pulls, which can be very memory-intensive, from pinning a server's resources.  There is limited support for mathematical expressions; +,-,*,\ and () are supported. You can also use the cpu variable which is resolved to the number of cpus that are available.

throttle.resource.scm-hosting.timeout=300

Controls how long threads will wait for SCM hosting operations to complete when the system is already running the maximum number of SCM hosting operations.

Value is in SECONDS.

throttle.resource.busy.message.timeout=5

Controls how long a warning banner is displayed in the UI after a request is rejected due to excessive load. 

Value is in MINUTES. Using 0, or a negative value, disables displaying the banner. 
This is deprecated and replaced by server.busy.on.ticket.rejected.within, It is due to be removed in Stash 3.0.

plugin.stash-scm-cache.expiry.check.interval=300

Controls how frequently expired caches are checked and deleted from disk.

Value is in SECONDS.

plugin.stash-scm-cache.minimum.free.space=1073741824

Controls how much space needs to be available on disk (specifically under <STASH-HOME>/caches) for caching to be enabled. This setting ensures that the cache plugin does not fill up the disk.

Value is in BYTES.

plugin.stash-scm-cache.protocols=HTTP,SSH

plugin.stash-scm-cache.refs.enabled=false

plugin.stash-scm-cache.refs.ttl=60

Controls how long the caches for ref advertisements are kept around when there no changes to the repository.

Caches are automatically invalidated when someone pushes to a repository or when a pull request is merged.

Time is in SECONDS.

plugin.stash-scm-cache.upload-pack.enabled=true

Controls whether clone operations are cached.

plugin.stash-scm-cache.upload-pack.ttl=14400

Controls how long the caches for clone operations are kept around when there no changes to the repository.

Caches are automatically invalidated when someone pushes to a repository or when a pull request is merged.

Time is in SECONDS.

plugin.stash-scm-git.path.executable=git

Defines the default path to the Git executable. On Windows machines, the .exe suffix will be added to the configured value automatically if it is not present. In general, "git" should be an acceptable default for every platform, here, assuming that it will be available in the runtime user's PATH. 

With the new path searching performed by DefaultGitBinaryHelper, setting a default value here is unnecessary, as the plugin will quickly discard the value. This is left here purely for documenting how to set an explicit path.

plugin.stash-scm-git.path.libexec=

Defines the path to the Git libexec directory (containing the git-core directory). This path is hard-coded into the Git executable and is used for forking processes like git-http-backend. If this value is set, Stash will directly fork out those processes. This eliminates an unnecessary fork (git -> git-http-backend) and may improve scalability.

plugin.stash-scm-git.backend.http.buffer.size=32768

Defines the buffer size in bytes which is used when marshaling data between the Git process and the HTTP socket.

plugin.stash-scm-git.backend.ssh.buffer.size=32768

Defines the buffer size in bytes which is used when marshaling data between the Git process and the SSH socket.

plugin.stash-scm-git.backend.timeout.idle=1800

Defines the idle timeout for push/pull processes, applying a limit to how long the operation is allowed to execute without either producing output or consuming input. The default value is 30 minutes. 

This value is in SECONDS.

plugin.stash-scm-git.backend.timeout.execution=86400

Defines the execution timeout for push/pull processes, applying a hard limit to how long the operation is allowed to run even if it is producing output or reading input. The default value is 1 day. 

This value is in SECONDS.

plugin.stash-scm-git.diff.renames=copies

Defines whether copy and/or rename detection should be performed. By default, both rename and copy detection are performed. Only files modified in the same commit are considered as rename or copy origins, to minimize overhead.

The possible settings are: 

• copy or copies – Applies --find-copies

• rename or renames – Applies --find-renames

• off – Disables rename and copy detection 

When using copy or copies, the value may optionally be suffixed with a "+" to use --find-copies-harder. This setting should be used with caution, as it can be very expensive. It considers every file in the repository, even files not modified in the same commit, as possible origins for copies. 

When copy and/or rename detection is enabled plugin.stash-scm-git.diff.renames.threshold can be used control the 
similarity index required for a change to be identified as a copy or rename.

plugin.stash-scm-git.diff.renames.threshold=50

Defines the threshold, as a percentage, for a file to be detected as a rename or a copy. This setting is only applied if copy and/or rename detection is enabled. The default threshold applied is 50% similarity (defined in Git itself). 

Git diff and Git diff-tree do not honor 100 (identical files only) for the threshold. They ignore the threshold and apply the default 50% threshold instead. A configured threshold of 100 will be applied as 99. Similarly, a configured threshold that is 0, or negative, will be applied as 1.

plugin.stash-scm-git.environment.variablesize=2000

Defines the maximum number of characters that can be added to a single environment variable. Different operating systems (and even different versions of the same operating system) have different hard limitations they apply to  environment variables. This default is intended to be low enough to work on all supported platforms out of the box, but still high enough to be usable. It is configurable in case it proves to be too high on some platform.

plugin.stash-scm-git.pullrequest.merge.auto.forceadd=false

Defines whether conflicted files should be added to the index using Git add --force, during automatic merges. By default, this behaviour is off – simple Git add is "safer". However, when merging across branches with discrepant .Gitignore settings, enabling this setting may allow the system to create a conflicted diff (where without it a diff to the common ancestor will be shown instead). 

Note: This value has no effect on real pull request merges. It is only applied during automatic merges, for producing a pull request's change tree and diff.

plugin.stash-scm-git.pullrequest.merge.auto.timeout=120

Defines the maximum amount of time any command used to perform a merge to support the "merge" diff mode is allowed to execute or idle. Because the commands used generally do not produce output, there is no separate idle timeout. 

This value is in SECONDS.

plugin.stash-scm-git.pullrequest.merge.real.timeout=300

Defines the maximum amount of time any command used to merge a pull request is allowed to execute or idle. Because the commands used generally do not produce output, there is no separate idle timeout. 

This value is in SECONDS.

server.busy.on.ticket.rejected.within=5

Controls how long a warning banner is displayed in the UI after a request is rejected due to excessive load. 

Value is in MINUTES. Using 0, or a negative value, disables displaying the banner.

server.busy.on.queue.time=60

Controls how long requests need to be queued before they cause a warning banner to appear. 

Value is in SECONDS. Using 0, or a negative value, disables displaying the banner.

mail.timeout.connect=60

mail.timeout.send=60 

mail.test.timeout.connect=30

mail.test.timeout.send=30

Controls timeouts for establishing an SMTP connection and sending an e-mail. Shorter timeouts should be applied for when sending test e-mails, as the test occurs in user time. 

Values are in SECONDS.

mail.error.pause.log=300

Controls how frequently logs will go to the standard log file about mail sending errors. All errors are logged to the atlassian-stash-mail.log file, but Stash will periodically log a warning to the standard log file if there are errors sending messages. 

Value is in SECONDS

mail.error.pause.retry=5

Controls how long Stash will wait before retrying to send a message if an error occurs. 

Value is in SECONDS

mail.threads=1

Controls the number of threads to use for sending emails. Setting this to a higher value will put greater load on your mail server when Stash generates a lot of emails, but will make Stash clear its internal queue faster.

mail.max.message.size=1048576

Controls the maximum allowed size of a single mail message, which is the sum of the subject and body sizes.

Value is in BYTES.

mail.max.queue.size=157286400

Controls the maximum allowed size for the mail queue (any new message will be rejected if the mail queue reaches that size).

Value is in BYTES.

plugin.ssh.command.timeout.idle=86400

Controls timeouts for all SSH commands, such as those that service Git and hg operations over SSH. The idle timeout configures how long the command is allowed to run without writing any output to the client. For SCM commands, the plugin.*.backend.timeout.idle properties defined above will be applied to the underlying process. The default value is 1 day. 

The value is in SECONDS.

Controls the language highlighter used for a given set of hashbang executables.

The <language> refers to the highlighter key defined by highlight.js.

Controls the language highlighter used for a given set of file extensions.

The <language> refers to the highlighter key defined by highlight.js.

plugin.com.atlassian.stash.plugin.hook.threadPoolCoreSize=2

plugin.com.atlassian.stash.plugin.hook.threadPoolMaxSize=3

plugin.com.atlassian.stash.plugin.hook.queueSize=1024

The maximum size of the queue which holds queued requests that are yet to be sent.

When this size is exceeded the oldest unsent message will be dropped and a warning message logged.

plugin.com.atlassian.stash.plugin.hook.connectionTimeout=10000

Connection timeout for hook request in MILLISECONDS.

When the connection times out a warning message will be logged.

plugin.com.atlassian.stash.plugin.hook.changesetsLimit=500

plugin.com.atlassian.stash.plugin.hook.changesLimit=100