CruiseControl.NET : SourceGear Vault Source Control Block
This page last changed on Jun 09, 2005 by orogers.
SourceGear Vault Configuration ExampleFor Visual Source Safe you must specify the executable, project, username and password. You may also specify the SSDIR. If SSDIR is not set the default or the SSDIR environment variable will be used.<sourcecontrol type="vault"> <executable>c:\program files\sourcegear\vault client\vault.exe</executable> <username>my_username</username> <password>my_password</password> <host>my_buildserver</host> <repository>my_repository</repository> <folder>$</folder> <ssl>True</ssl> </sourcecontrol> Configuration Elements:
*: it is possible to deposit these values with the Vault client so that they do not need to be stored in the ccnet.config file. Getting the latest source from VaultNOTE: as of 0.9.2, CCNet now supports automatically getting the latest version of the source from Vault. The NAnt bootstrap file is no longer necessary.Filtering out Label ChangesVault interprets new labels as changes, so if you apply a label as part of your build process, this will kick off another build. To get around this, use a Filtered Source Control Block. If your build server uses a specific user id to integrate with Vault, you can set up a UserFilter to filter out all changes made by that user.Problems with CCService and Vault 3.0.2+If you are experiencing problems detecting modifications using CCService after upgrading to Vault 3.0.2, it may be related to the enhanced security features of the Vault server. You should try the following process to fix this issue:
Code contributed by Ryan Duffield and Leo von Wyss. |
Document generated by Confluence on Jun 26, 2005 17:23 |