For example, if your working copy has version 1.5, you will not be able to use Subversion 1.4 binaries to work with it. If you run command-line svn commands on the files checked out by TeamCity. The specified format is important in two cases: svn directories, when the checkout on agent mode is used. This option defines the format version of Subversion files located in. Available values for this option are 1.4 through 1.8 (current default). if you have a build configuration which uses a combination of this VCS Root + VCS Checkout Rules referencing a non-restricted path above the restricted one for another build configuration, changes under the restricted path will be ignored even if you specify correct username/password for the VCS Root itself. This rule only applies for svn:// and http(s):// protocols i.e. Note that if you have anonymous access for some path within SVN, the entered username will never be used to authenticate when accessing any of its subdirectories. If enabled, TeamCity is able to connect to SVN servers without properly signed SSL certificate. HTTPS Connections: Accept non-trusted SSL certificates If you have 2 different repositories with the same UUID (due to repository copy) TeamCity may function incorrectly, for instance, wrong HEAD revision of an external repository can be checked out.
TeamCity relies on Subversion repository UUID as an unique identifier of a repository. Ignore externals: TeamCity will ignore any configured svn:externals property, and thus TeamCity will not check for changes or check out any source file from the SVN externals. For other two options, TeamCity takes the revision of the latest detected change as the revision for a checkout. If you use the " Checkout, but ignore changes" option, TeamCity will always use the latest repository revision as the revision for a checkout (the same revision will be used for the parameter). You can use this option if you have several SVN externals and do not want to get information about any changes made in the externals' source files. Note that versioned settings may be affected as enabling this option will cause timestamps to be added to revisions.Ĭheckout, but ignore changes: TeamCity will check out the sources from externals but any changes in externals' source files will not be gathered and displayed on the Changes tab. Select one of the following options to control the SVN externals processing.įull support (load changes and checkout): TeamCity will check out all the configuration's sources (including the sources from the externals) and will gather and display information about externals' changes on the Changes tab.
TeamCity does not store authentication in SVN configuration directory, but can read settings stored there.Įnable this option to make this the default configuration directory for the SVN connection. This setting also applies to agent-side checkout. You can specify an alternative Subversion configuration directory, or use the default one (recommended). Specify the SVN URL that points to the project sources.
0 kommentar(er)
