Stages Documentation

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
74:cms_subversion [2020/05/19 16:25] – tssr74:cms_subversion [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
 ==== Subversion ==== ==== Subversion ====
 +
 +Stages supports SVN 1.9, 1.10 and 1.14
  
 === Example Configuration === === Example Configuration ===
Line 14: Line 16:
     </cms-host>     </cms-host>
 </cms-type> </cms-type>
 +
 +
 </code> </code>
  
 === Host Properties === === Host Properties ===
-These configuration properties affect the behavior of one SharePoint Online server. 
  
-** * ** ''Required''\\+These configuration properties affect the behavior of one Subversion server. 
 + 
 +*** ** ''Required'' \\
 Properties marked with ** * ** are required for the adapter to work. Properties marked with ** * ** are required for the adapter to work.
  
-** # ** ''Required but can also be set in web-application''\\+**# ** ''Required but can also be set in web-application'' \\
 Properties marked with ** # ** are required but can also be set in the //File Management// section in the Stages web-application as well. The value entered in the web-application overrides the one from the config.xml. Properties marked with ** # ** are required but can also be set in the //File Management// section in the Stages web-application as well. The value entered in the web-application overrides the one from the config.xml.
  
-** + ** ''Required but with default''\\+**+ ** ''Required but with default'' \\
 Properties marked with ** + ** are required, but there is a default value. This values can be overridden by configuring it in the config.xml. Properties marked with ** + ** are required, but there is a default value. This values can be overridden by configuring it in the config.xml.
  
 > user ** # ** > user ** # **
  
-  * __Description__: You may enter the Subversion username for the Stages system account here instead of the corresponding field Username in the cms profile. If both values exist, the username from the cms profile is preferred.+   * __Description__: You may enter the Subversion username for the Stages system account here instead of the corresponding field Username in the cms profile. If both values exist, the username from the cms profile is preferred. 
 +The Subversion user needs read and write access to the repository.
  
 > password ** # ** > password ** # **
  
   * __Description__: You may enter the Subversion password for the Stages system account here instead of the corresponding field Password in the cms profile. If both values exist, the password from the cms profile is preferred.   * __Description__: You may enter the Subversion password for the Stages system account here instead of the corresponding field Password in the cms profile. If both values exist, the password from the cms profile is preferred.
- 
 > http.connection.timeout ** + ** > http.connection.timeout ** + **
  
   * __Default Value__: 30000   * __Default Value__: 30000
   * __Description__: The timeout in milliseconds until a http connection has to be established and the maximum period of inactivity (in milliseconds) between two consecutive data packets before the socket is closed.   * __Description__: The timeout in milliseconds until a http connection has to be established and the maximum period of inactivity (in milliseconds) between two consecutive data packets before the socket is closed.
- 
 > http.max.connections ** + ** > http.max.connections ** + **
  
   * __Default Value__: 100   * __Default Value__: 100
   * __Description__: The maximum number of simultaneously used http connections between Stages and the Subversion server.   * __Description__: The maximum number of simultaneously used http connections between Stages and the Subversion server.
- 
 > http.ssl.allow.all ** + ** > http.ssl.allow.all ** + **
  
   * __Default Value__: false   * __Default Value__: false
   * __Description__: When set to true, disables any verification checks for certificates in case of ssl-secured https connections. It is recommended to only use this in test environments where no valid certificates exist (e.g. self-signed certificates).   * __Description__: When set to true, disables any verification checks for certificates in case of ssl-secured https connections. It is recommended to only use this in test environments where no valid certificates exist (e.g. self-signed certificates).
- 
 > use.system.account.for.download ** + ** > use.system.account.for.download ** + **
  
   * __Default Value__: false   * __Default Value__: false
   * __Description__: When set to true, files will be downloaded from stages using the system account.   * __Description__: When set to true, files will be downloaded from stages using the system account.
- 
 > domain > domain
  
   * __Description__: You may enter the Subversion default domain for the Stages system account, and all user accounts. (Only necessary for ntlm authentication)   * __Description__: You may enter the Subversion default domain for the Stages system account, and all user accounts. (Only necessary for ntlm authentication)
- +> http.authentication.hostname (required for ntlm authentication)
-> http.authentication.hostname  (required for ntlm authentication)+
  
   * __Description__: The host name of the server that runs Stages and is allowed to authenticate via ntlm against the Subversion server   * __Description__: The host name of the server that runs Stages and is allowed to authenticate via ntlm against the Subversion server
- 
 === Repository Configuration === === Repository Configuration ===
-Access to Subversion projects can be configured in Stages processes via “Management > File Management > Repositories”. 
-{{ :cms:svn-repository.png? |}} 
  
-> Name: +Access to Subversion projects can be configured in Stages processes via “Management > File Management > Repositories”. [[https://doc.stagesasaservice.com/lib/exe/detail.php?id=74:cms_subversion&media=cms:svn-repository.png|{{  :cms:svn-repository.png  }}]]
-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: +> Name: The name of this Subversion configuration. This name will be used by Stages to refer to this repository configuration (e.g. in repository plan)
-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 +> 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. 
-Define the path to the Subversion repository. This overwrites the **path** from the URL entered in the configuration file (config.xml).+ 
 +> Repository Path Define the path to the Subversion repository. This overwrites the **path**  from the URL entered in the configuration file (config.xml).
  
 Example: 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 +  * **config.xml**: //<nowiki><cms-host name="http://mySubversion.de:123/myPath/to/myRepository" /></nowiki>// 
-  * Resulting URL: <nowiki>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/another/Repository</nowiki>//
   * The path from the config.xml gets overwritten by the value from Repository Path.   * The path from the config.xml gets overwritten by the value from Repository Path.
  
-> Enforce Usage of System Account +> 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. 
-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: Define a username for this repository configuration. This overwrites the property **username**  from the configuration file (config.xml). 
 + 
 +> Password Define a username for this repository configuration. This overwrites the property **password**  from the configuration file (config.xml). 
 + 
 +> Default Lifecycle Select a lifecycle from the process metamodel as default for files from this repository. 
 + 
 +==== Known Limitations ====
  
-> Username: +== svn:needs-lock is actually not supported by Stages ==
-Define a username for this repository configuration. This overwrites the property **username** from the configuration file (config.xml).+
  
-> Password +If the svn attribute "svn:needs-lock" is set for a file this will be ignored by Stages
-Define a username for this repository configuration. This overwrites the property **password** from the configuration file (config.xml).+
  
-> Default Lifecycle 
-Select a lifecycle from the process metamodel as default for files from this repository.