Configuring Access to the VCS Repository
Important: The feature described in this section is required for Visual SourceSafe and Subversion.
In a shared development environment, a software developer might have one user name on Integration Server and a different user name on the VCS server. The VCS Integration feature accommodates this by enabling you to map an Integration Server user to a VCS user.
Integration Server users gain access to the VCS server by being mapped to a VCS user name and password. If you make changes to the VCS user name or password, you must edit the mapping to reflect the changes. For example, if you change the VCS user password, you must change the VCS user password in the mapping.
Each Integration Server user can map to only one VCS user. If you want to access the VCS server using different VCS users at different times, you can edit your mapping each time you want to use a different VCS user, or you can set up multiple Integration Server users and map each one to a different VCS user.
When you check in or delete a file, the VCS Integration feature records both the
Integration Server user and the VCS user as part of the VCS revision history. For more information on working with multiple user accounts in a shared development environment, see
Understanding Multiple User Accounts
and VCS Integration.
If you are an Integration Server user with administrator privileges, you can also create mappings for other Integration Server users.
Note: Only map multiple Integration Server users to one VCS user if this behavior is required in your environment. Depending on your VCS, mapping multiple Integration Server users to a single VCS user might result in errors or unpredictable results. In addition, you might have difficulty tracing a VCS action back to a particular Integration Server user.