Server Limits

This section describes the configurations to help protecting the server from being overloaded by too many requests.

Configuration File

You can also configure all of these settings using a configuration file.

Pre-Commit Limits

Pre-commit analysis is triggered from the IDEs by developers. If a high number of developers is using this feature, a considerable number of requests is sent to the Teamscale server. The maximum number of files and the maximum individual file size per pre-commit as well as the minimum waiting time between pre-commit requests can be configured.

Pre-Commit Limits for Cloud-Hosted Instances

For instances hosted on our cloud platform, this setting is automatically configured and cannot be changed.

Late External Upload Processing

When external analysis data (for example, coverage) is uploaded to Teamscale, a rollback is performed to integrate the external data with code from the repository. Especially for old uploads that require a rollback of several days, the following reanalysis can take a considerable amount of time. As a solution to this problem, Teamscale can postpone these uploads to a time when such a reanalysis does not disrupt normal operation, for example, during the night.

The setting requires a crontab expression that defines at which time rollbacks and reanalysis from those late uploads may be performed, for example, 0 21 * * * for every day at 21:00. The setting is active if a non-empty crontab expression is provided.

The age threshold defines how many minutes an upload must lie in the past to be considered late. Teamscale compares the timestamp of the commit the upload refers to with the newest commit it has already processed in the project. The time at which the upload is made or the report is generated does not matter. The default threshold is 60 minutes.

For recommended values, see Best Practices for Coverage Uploads.