Differences

This shows you the differences between two versions of the page.

--- 74:cms_subversion [2020/05/19 16:23] – tssr
+++ 74:cms_subversion [2020/05/19 16:38] – tssr
@@ Line 71: / Line 71: @@
 The name of this Subversion configuration. This name will be used by Stages to refer to this repository configuration (e.g. in repository plan)
-> Server:
+> Subversion Server:
 This selection field contains an entry for each cms-host section in the Stages configuration file (config.xml). You can select the host for this repository configuration.
+> Repository Path
+Define the path to the Subversion repository. This overwrites the **path** from the URL entered in the configuration file (config.xml).
+Example:
+  * **config.xml**: //<nowiki><cms-host name="http://mySubversion.de:123/myPath/to/myRepository" /></nowiki>//
+  * Value in  **Repository Path**: //myPath/to/another/Repository//
+  * Resulting **URL**: //<nowiki>http://mySubversion.de:123/myPath/to/myRepository</nowiki>//
+  * The path from the config.xml gets overwritten by the value from Repository Path.
+> Enforce Usage of System Account
+If this is set to //true//, Stages will use the user credentials from this repository configuration for **ALL** operations. This means, every check-in, download or lock operation will be executed with the same username.
 > Username:
@@ Line 83: / Line 95: @@
 Select a lifecycle from the process metamodel as default for files from this repository.
-> Repository Path
-Define the path to the Subversion repository. This overwrites the **path** from the URL entered in the configuration file (config.xml).
-Example:
-  * Configuration file (config.xml): <nowiki><cms-host name="http://mySubversion.de:123/myPath/to/myRepository" /></nowiki>
-  * Value in  Repository Path: myPath/to/another/Repository
-  * Resulting URL: <nowiki>http://mySubversion.de:123/myPath/to/myRepository</nowiki>
-  * The path from the config.xml gets overwritten by the value from Repository Path.
-> Enforce Usage of System Account
-If this is set to //true//, Stages will use the user credentials from this repository configuration for **ALL** operations. This means, every check-in, download or lock operation will be executed with the same username.