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/08/27 13:56] – [Known Limitations] fkjn74: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>
Line 19: Line 22:
 === Host Properties === === Host Properties ===
  
-These configuration properties affect the behavior of one SharePoint Online server.+These configuration properties affect the behavior of one Subversion server.
  
 *** ** ''Required'' \\ *** ** ''Required'' \\
Line 33: Line 36:
  
    * __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 ** # **
  
Line 62: Line 67:
 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  }}]] 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  }}]]
  
-> 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)+> 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)
  
-> 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.+> 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).+> 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:
Line 75: Line 80:
   * 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  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.+> 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:  Define a username for this repository configuration. This overwrites the property **username**  from the configuration file (config.xml).+> 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).+> 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.+> Default Lifecycle Select a lifecycle from the process metamodel as default for files from this repository.
  
 ==== Known Limitations ==== ==== Known Limitations ====