...
- whether the synchronization settings are the same as in the parent project
- whether the synchronization is enabled.
- when synchronization is enabled, you can define which settings to use when build starts. See details below.
which VCS Root is used to store the project settings: you can store the settings either in the same repository as the source code, or in a dedicated VCS root.
...
| Warning |
|---|
If this option is not enabled, the security implications listed below should be taken into account before committing security data to the VCS. |
...
It is recommended to store passwords, API tokens, and other secure settings outside of VCS using the corresponding option described above.
Note that SSH keys will not be stored in the VCS repository.
...
| Warning |
|---|
Before committing settings to the VCS, consider the recommended approach to storing security settings described above. |
If you want to commit the current configuration to the VCS (e.g. earlier you committed misconfigured settings to the repository and TeamCity was unable to load it displaying errors and warnings), you can use the Commit current project settings... option on the Versioned Settings | Configuration page.
When TeamCity commits settings into a VCS, it uses a standard commit message noting the TeamCity user as the committer and the project whose settings changed. Since TeamCity 10.0, it is possible to add a fixed custom prefix to each settings change commited by TeamCity via the teamcity.versionedSettings.commitMessagePrefix internal property, e.g. teamcity.versionedSettings.commitMessagePrefix=TC Change\n\n
...