Enabling your users to integrate Perforce repositories into their TeamForge projects requires some extra configuration.
-
If you are adding Perforce support to an existing site, back up your site's
data first. (If you are adding Perforce as part of installing a new site, skip
this.)
See Back up CollabNet TeamForge data.
-
Install Perforce, using the instructions in the Perforce sysadmin documentation.
-
Open the site-options.conf file.
This is the master configuration file that controls your TeamForge site.
-
vi /opt/collabnet/teamforge-installer/8.0.0.1/conf/site-options.conf
Note: vi is an example. Any *nix text editor will
work.
-
Add these variables to your site-options.conf file,
changing the values as appropriate:
Note: In case of a multi-server setup, modify the token
PERFORCE_PORT=0.0.0.0:1666 in the
site-options.conf file in all the boxes where the
service is distributed to get the correct status of the Perforce
server.
- PERFORCE_PORT=localhost:1666
- PERFORCE_CLIENT=/usr/local/bin/p4
- PERFORCE_LICENSE_FILE=/tmp/license
-
Review the variables you've changed, then save the
site-options.conf file.
-
If your Perforce server is running SUSE, remove the perforce user from the
TeamForge server and bootstrap the
site data. (If you are on Red Hat or CentOS, skip this.)
- userdel perforce
- ./bootstrap-data.sh
-
If you are adding Perforce support to an existing site, restore your site's
data.
See Restore backed-up CollabNet TeamForge data.