ServerGlobalSettings
Stores global TeamCity server settings that affect all projects on this server. These settings are accessible via TeamCity UI from the Admin | Global Settings page. Use the /app/rest/server/globalSettings to view and edit these settings.
Properties
rootUrl
The TeamCity server URL.
defaultVCSCheckInterval
An Integer value that specifies how often (in seconds) TeamCity polls VCS repositories for changes. The default value is 60 seconds.
enforceDefaultVCSCheckInterval
true, if project administrators cannot set the polling interval in VCS root settings lower than the defaultVCSCheckInterval; otherwise, false.
useEncryption
true if TeamCity encrypts all sensitive values using a custom key; false if it uses the defaul scrambled mechanism for these values.
artifactsDomainIsolation
true if TeamCity publishes build artifacts to a separate domain; false if the artifacts can be accessed from the regular TeamCity server URL.
artifactsUrl
If artifactsDomainIsolation is set to true, this property returns the URL of the artifacts isolation domain.
encryptionKey
Returns the encryption key. This property is hidden from the payload.
artifactDirectories
A String containing the concatenated paths to the artifact directories used by the server. Paths are separated using the new line characters.
defaultQuietPeriod
The delay (in seconds) between a moment TeamCity detects a new VCS change and a moment a new build processing this change starts. Individual build configuration triggers can override this global setting.
defaultExecutionTimeout
The maximum allowed build duration. Zero or negative values mean no time limit.
maxArtifactsNumber
The maximum number of artifacts that can be published per build, or -1 if there is no limit. This number does not include hidden artifacts.
maxArtifactSize
The maximum allowed artifact size (in bytes), or -1 if there is no size limit. Artifacts that exceed these limit will not be published.
Schema
Below, you can find a full schema of this object, in XML and JSON formats. You can choose what fields to submit depending on your current needs. Different methods might expect different fields: the best approach is to request this entity via GET and use the response as a base for the following POST request.
A link to another object implies that you can substitute it with the schema of the linked object, if it is required for your call.