Provide source control services

You can add a source control server to the CollabNet TeamForge environment at any time after CollabNet TeamForge installation is complete.

• Integrate a source code server
  A site must have one or more servers to handle source code repositories and users. The source code server can be the same machine as the application server or a separate machine.
• Approve a source control repository request
  When a user requests a source code repository on a source control server for which you have required approval, a CollabNet TeamForge administrator must approve the request before the repository is created.
• Approve an unmanaged CVS server access request
  When a user asks for access to an unmanaged CVS server, an administrator must approve or reject the request.
• Edit SCM integration details
  You can move or reconfigure a source control server without having to reintegrate the server into CollabNet TeamForge .
• Move a source code repository
  When the existing code base for an application may need to be managed by a different team or project, you can move the source code repository from the first project into the other one.
• Connect to a Subversion Edge console
  When a Subversion Edge server has been converted to a SCM Integration server in TeamForge, you can log into its management console from within TeamForge.
• Discover a Subversion Edge server
  Subversion Edge (version 1.1 and higher) servers register their service on your local network using the DNS-Service Discovery protocol. TeamForge administrators can see them.
• Manage replicas
  A replica server in TeamForge is a Subversion Edge server that replicates the content of an existing core SCM integration server.
• Integrate an unmanaged CVS repository with CollabNet TeamForge
  After creating the repository, you must modify two triggers, verifymsg and loginfo, to complete the integration with CollabNet TeamForge .