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 revisionBoth sides next revision
74:cms_subversion [2020/08/27 13:56] – [Known Limitations] fkjn74:cms_subversion [2021/03/09 15:09] – mir
Line 2: Line 2:
  
 ==== Subversion ==== ==== Subversion ====
 +
 +Stages supports SVN 1.7, 1.8 and 1.9
  
 === Example Configuration === === Example Configuration ===
Line 14: Line 16:
     </cms-host>     </cms-host>
 </cms-type> </cms-type>
 +
  
 </code> </code>
Line 62: Line 65:
 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 78:
   * 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 ====