...
Subversion Configuration
Parasoft’s Subversion support is based on the command line client 'svn'. See About Source Control Support for a list of supported SVN versions.
The client certificate must be stored in the Subversion configuration area. The Subversion client has a built-in system for caching authentication credentials on disk. By default, whenever the command-line client successfully authenticates itself to a server, it saves the credentials in the user's private runtime configuration area—in ~/.subversion/auth/ on Unix-like systems or %APPDATA%/Subversion/auth/ on Windows.
When you are enabling source control support, specify the following repository properties in the Create Source Control Description dialog:
- URL: Enter the URL for the SVN server. The URL should specify the protocol, server name, port and starting repository path (for example, svn://buildmachine.foobar.com/home/svn).
- User: Enter the user name under which you want to connect to the repository.
- Password: Enter the password (not encoded) for the above user name.
Team Foundation Server Configuration
...
By default, SOAtest uses the cached credentials for accessing TFS (this could be your user login or some previously logged in information). You can provide custom credentials if you want to use them instead of the cached ones.
Specifying Source Control Definitions via
...
localsettings
Source control definitions can be specified in settings localsettings (e.g. for sharing team-wide settings via DTP, Concerto, or by specifying options at the command line). See See Configuring SettingsLocalsettings for details.